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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety profile is clear. The description adds valuable context: MCP cannot return binary data, so the zip is saved to a temporary file and the path and size are returned. This explains behavior beyond annotations, though it could mention file persistence or cleanup.

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?

Two sentences, front-loaded with the core action and followed by essential behavioral context about the return value. No wasted words.

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 read-only export tool with rich annotations and full schema coverage, the description adequately explains the return value (file path and size) and the temporary file workaround. An output schema is absent, but the description covers what is returned.

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 parameters (context, framework, project_id) are fully documented in the schema. The description adds no additional parameter semantics; baseline 3 is appropriate.

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 'Export' and resource 'project's test framework as a zip archive', clearly distinguishing it from export_project_as_qtml (which exports QTLM). However, it does not explicitly name alternatives or state differentiation, leaving some inference to the agent.

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?

The description implies usage (when you need the framework files as a zip) but provides no explicit when-to-use, when-not-to-use, or alternative tools. The agent must infer from context that this is the right export format versus siblings like export_project_as_qtml.

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