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

Annotations already mark this as a non-read-only, non-idempotent, non-destructive write. The description adds real behavioral context: it runs synchronously ('runs at once'), returns the topic id, and names are unique per project ignoring case, which implies duplicate-name behavior. It stops short of stating what error occurs on a duplicate name.

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 sentences, each earning its place: definition first, execution/return behavior second, uniqueness constraint last. No filler or restatement of the tool name.

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 3-parameter mutation with no output schema, the description supplies the return value (topic id) and its downstream use, plus creation semantics. It omits error behavior on duplicate names and any permission requirements, which are the only remaining gaps.

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, but the description adds meaning the schema lacks: the name-uniqueness rule is case-insensitive, and the returned id's relationship to project_id/topic_id linkage is spelled out. The optional description parameter's purpose is left to the schema.

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?

'Add a topic' states the specific verb and resource, then defines what a topic actually is ('a named group of tracked prompts ... that visibility is broken down by') with concrete examples. An agent can distinguish this from delete_topic or rename_topic from the name alone.

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?

The description clarifies downstream usage by stating the returned topic_id is passed to prepare_add_prompts to file prompts under it, which establishes the creation workflow. It doesn't explicitly exclude alternatives (e.g., whether topics can be created implicitly elsewhere), so it falls short of full when/when-not guidance.

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