Export project as JSON content

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower; the description still adds real value by disclosing that runtime fields are stripped and a version is stamped, matching the app's export serialization. It stops short of covering failure modes such as an unknown project id or payload size, which keeps it from a 5.

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 dense sentences front-load the action and the key caller responsibility, with zero filler in between. The trailing 'Read-only.' merely restates the readOnlyHint annotation and is the one piece that does not earn its place.

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?

With one required parameter, full schema coverage, and no output schema, the description does the necessary work: it explains what the returned content is and that the caller must write it to a file. Only error/edge-case behavior is unaddressed, which is a minor gap for a simple read tool.

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?

There is a single parameter with 100% schema description coverage ('Project configId (from project_list)'), so the schema already carries the semantics. The description adds no further detail about the id, making the baseline 3 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?

The description names a specific verb and resource ('Export a project's config as JSON content') and immediately clarifies the scope of the output versus the app's own save flow. The line 'No save dialog; write the returned content to a file yourself' implicitly separates it from the mutating project_save sibling, so an agent can pick correctly without opening schemas.

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 makes clear that this returns content rather than persisting it, which implies the usage context (agent wants the JSON payload). However, it never explicitly says when to prefer this over project_save, nor does it name any alternative or exclusion — the routing has to be inferred from behavior.

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