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

Annotations already establish that this is a non-read-only, non-destructive write, so the safety profile is covered. The description adds the hierarchical-placement behavior (content lands near its named parent), which is not encoded in annotations. It remains silent on permissions, duplicate handling, and whether a missing category silently becomes top-level.

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 compact sentence with the placement behavior front-loaded and no filler. It is efficient, though its terseness is part of what leaves the parameters undocumented.

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 7-parameter mutation tool with 0% schema coverage and no sibling differentiation, the description covers only category_name placement. Output schema exists so return values need not be explained, but the meaning of map_id, idempotency_key, language, and the required content fields is missing, as is any guidance against the sibling tools.

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 0% across 7 parameters (map_id, content, summary, language, idempotency_key, title all undocumented). The description clarifies only category_name, leaving six parameters with no semantics anywhere, including the null-defaulted map_id and idempotency_key whose purpose is entirely unexplained.

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?

The description names a concrete verb ('Add') and resource ('topic') and specifies placement relative to a parent category, so the agent knows this inserts content into a map hierarchy. It does not, however, differentiate itself from siblings like create_topic_at_position or suggest_connection, leaving the reader to infer the distinction.

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 one explicit conditional rule ('omit category_name for a top-level topic'), which is genuine usage guidance for one parameter. But it never states when to use this tool versus create_topic_at_position, suggest_connection, or the other map-mutating siblings, so routing guidance is only implied.

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