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

Annotations only declare the safety profile (readOnly false, openWorld true, destructive false); the description adds genuinely new behavior — that it is state-changing, that it runs 'after authorization', and that targeting a public Space makes the content publicly accessible. That public-exposure warning is exactly the kind of consequence an agent needs. No idempotency or duplicate-handling detail, so not 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?

Three short clauses ordered as trigger, behavior/consequence, then parameters — well front-loaded with no filler. Slightly dense in the first clause, but nothing wasted.

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 4-param create operation with full schema coverage and safety annotations, the description covers purpose, side effects and required inputs adequately. With no output schema present, it could say what is returned (e.g. the new Space item ID), which is the only real gap.

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 coverage is 100% and each parameter already carries its own description (including 'Call list-spaces first' / 'Call list-generations first'), so the schema does the heavy lifting. The description only restates which params are required and optional, adding no format or constraint detail beyond the schema — baseline 3.

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 ('add/save/publish') and resource ('existing generated output/result') into a documentation Space. The word 'existing' cleanly separates it from generate-and-add-documentation and generate-*-and-add siblings, which produce content rather than filing an already-produced generation.

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 opening clause gives an explicit trigger ('when the user wants to save, publish, or add an existing generated output'), which is clear usage context. It stops short of naming an alternative or a when-not condition, so it falls just below a 5.

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