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

Annotations already declare non-destructive and idempotent, and the description adds useful behavioral context beyond them: a hard constraint (default reports can't be renamed) and a workflow prerequisite (read first). It does not cover permission/org requirements, but adds genuine value over the annotations.

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 sentences, front-loaded with the action, then the constraint and prerequisite. No filler—every clause carries actionable 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?

An output schema covers return values, and the description supplies the constraint and prerequisite for a simple rename mutation. Only minor gaps remain around org context and parameter nuances, which are mostly handled by the schema.

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 only 25% (only organization_id is documented), and the description compensates minimally—'in its session' loosely maps to session_id but adds no constraint or format detail for name or output_id. The params are largely self-explanatory by name, so a mid score fits.

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 (rename) and resource (Studio output in its session), which is distinct from rename_research_session. It does not explicitly name sibling alternatives, but the resource scope is unambiguous enough to differentiate.

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?

Gives a clear prerequisite ('Read the output first') and a when-not clause ('Default reports cannot be renamed'), which sets real guardrails for correct invocation. It lacks explicit routing to alternatives like edit_research_output, so not a 5.

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