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

Goes well beyond annotations (which only say non-read-only, idempotent, non-destructive): it discloses that data is preserved ("prompts and past results stay under it"), that it executes immediately, that it returns the new name, and the two refusal conditions (name collision, foreign topic_id). This is exactly the mutation-safety context an agent needs.

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 sibling routing, then execution/failure behavior. No filler; every clause carries information an agent would otherwise have to guess.

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?

No output schema exists, and the description supplies the return value ("returns the new name") plus failure modes. For a 3-required-param mutation tool, an agent has everything needed to decide, call, and interpret the result.

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%, so the baseline is 3. The description adds a real constraint not obvious from the schema: topic_id must belong to the given project, and name must be project-unique or the call is refused — meaningful semantics beyond field types.

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?

Specific verb+resource: "Rename one topic," with an explicit scope of exactly one topic. It distinguishes itself from the two nearest siblings (delete_topic, create_topic) by naming them and stating the condition that selects this tool.

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?

Explicit alternative routing: "prefer this to delete_topic and create_topic when only the name is wrong." It also states a precondition ("after the user agrees"), so the agent knows a confirmation gate applies before calling.

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