Export analysis

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

Annotations already declare this is destructive, non-read-only, and idempotent, so safety semantics are covered structurally. The description adds useful context that the tool returns the destination path and file size, which is not in an output schema, but it does not mention the existing-file refusal or overwrite behavior even though those are documented in the schema. With annotations carrying the safety profile, this is adequate but not rich.

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?

The description is two tight sentences with no filler. The primary action and return values come first, followed by the routing guidance, so it is well front-loaded.

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 export tool, the description covers what it does, when to use it, and what it returns. The input schema handles all parameter details including overwrite and refusal behavior, and annotations cover the mutation safety profile, so nothing critical is missing from the definition as a whole.

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 the input schema already fully documents targetId, path, and overwrite. The description does not add parameter-level detail beyond what the schema provides, which is appropriate for high coverage but warrants the baseline score.

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 states a specific verb and resource: writing the complete analysis as JSON to a file. It also front-loads the return values (path and size) and distinguishes the operation from paging, so an agent can immediately tell what this tool does and how it differs from list-style siblings.

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?

It explicitly says to use this instead of paging when the agent needs everything, which is direct guidance for selecting this tool over an alternative. It stops short of describing when not to use it, such as for small results where paging is sufficient, but the primary routing condition is clear.

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