Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a non-destructive mutation without external side effects. The description adds that it creates a project and/or test cases, but does not say whether an existing project_id is modified in place, whether existing test cases are appended or replaced, or what is returned on success — the details that matter most for a write tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is slightly under-specified rather than verbose, and 'and/or' costs precision without buying length savings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Not applicable — hmm, adjust below.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are already documented, and the description mostly restates them. It does not clarify the interaction between project_id and create_project (e.g., that project_id overrides create_project), which is the one semantic gap the schema leaves implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Import') and resource ('QTML source string') plus the resulting artifacts (project and/or test cases), which is clear on its own. However, it doesn't distinguish itself from sibling tools in the same family (parse_qtml, validate_qtml, convert_qtml_to_playwright, export_project_as_qtml), and 'and/or' leaves the output shape ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this instead of parse_qtml, validate_qtml, or import_test_cases_from_document. The agent must infer usage from the name alone; nothing addresses prerequisites such as whether the QTML should be validated first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.