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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful piece of context beyond that: the result is a 'document string' rather than a file download, which affects how the agent should handle the output. No mention of permissions, size limits, or included metadata.

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 sentence with no filler; the verb, resource, and return type are all front-loaded. Nothing could be removed without losing information.

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?

For a simple read-only export with full schema coverage, the description covers what is exported and that the result is a string. There is no output schema, but the 'document string' phrasing compensates adequately; only edge cases (very large projects, error behavior) are left unspecified.

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 all three parameters (including the verbose context field) are documented in the schema itself. The description's phrase 'and its test cases' aligns with the optional test_case_ids parameter but adds no syntax or defaulting guidance beyond the schema's 'omit for all'.

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?

The description names a specific verb (export) and resource (a project and its test cases) plus the output format (QTML document string), which clearly separates it from siblings like export_framework or convert_qtml_to_playwright. It never explicitly names a sibling, so no explicit differentiation is provided.

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 tool versus parse_qtml, validate_qtml, convert_qtml_to_playwright, or export_framework. An agent must infer the use case entirely from the verb and resource.

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