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

Annotations already declare a non-destructive, idempotent, closed-world write. The description adds genuine context beyond them: only the label changes and the session's sources and analysis are left intact, which is the key side-effect question for a rename mutation. It omits permission requirements and failure modes.

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?

A single front-loaded sentence with no filler; the mutating action and its blast radius land immediately. Nothing in it is redundant with structured fields.

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?

Output schema exists, so return values need not be described, and annotations cover the safety profile. Still, for a mutation with an undocumented UUID parameter and an org-scoping parameter, the description leaves the agent guessing about targeting and preconditions.

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 33% — just organization_id is documented — so the description must carry the rest and does not. 'One organization Hub session' vaguely gestures at organization scoping, but nothing is said about session_id (UUID of the target session), whether the name must be unique, or how collisions/duplicate labels are handled.

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 ('organization Hub session'), plus a scope qualifier ('without changing its sources or analysis'). An agent can distinguish it from delete_research_session or rename_research_output by the resource named, though the sibling rename_research_output is never explicitly contrasted.

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?

Usage is implied by the verb/resource pair — rename an existing session when its label is wrong. There is no explicit guidance on when to prefer this over alternatives, no prerequisites (ownership/active membership, whether the session must be idle), and no exclusions.

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