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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is carried structurally, but the description adds nothing: it doesn't say whether omitted fields are preserved, whether passing null clears the description, or whether the rename can collide with an existing topic name. For a mutation flagged destructive, that silence is a real gap.

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, which is structurally good, but the brevity comes at the cost of substance rather than being earned concision.

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 three-parameter destructive mutation with no output schema and no sibling differentiation, one short sentence leaves too much uncertain: partial-update semantics, null handling, and error conditions are all unstated.

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 description coverage is only 33% — only id is documented. The description implies name and description map to "rename" and "describe," but it doesn't explain that description is nullable (i.e. can be cleared) or reference the 60/200 maxLength constraints that would cause calls to fail.

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?

"Rename or describe a topic" gives a verb (rename) and a resource (topic), and the verb distinguishes it from get_topic, create_topic and delete_topic. But "describe a topic" is ambiguous — it could be read as retrieving a description rather than setting the description field, so the actual effect is not fully pinned down.

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?

There is no guidance on when to use this vs create_topic, delete_topic, get_topic or set_contact_topic, and no prerequisites or field-level conditions are stated. The agent has to infer usage entirely from the name.

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