remove_topic

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

The description discloses that no error is returned if the topic is not present (idempotent delete), which is a key behavioral trait. It also specifies the topic name format, adding transparency beyond the schema. No annotations exist, so the description carries full burden and fulfills it.

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?

The description is two sentences: first covering purpose and idempotency, second covering naming rules and user confirmation. Every sentence adds essential information with no redundancy. Front-loaded and concise.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description covers purpose, idempotent behavior, naming rules, and a usage guideline. It does not describe return values or potential errors, but the context is manageable. Slightly above average completeness.

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?

The input schema has 100% description coverage for all three parameters. The description adds minimal semantic value for parameters (e.g., 'by name'), but the schema already explains defaults for repo and owner. The confirmation guideline is not parameter-specific. Baseline 3 is appropriate.

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 states 'Remove ONE topic from a repository by name' with a specific verb and resource, and distinguishes from sibling tools like add_topic or replace_topics. It also mentions idempotent delete and naming rules.

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 instructs 'Confirm with the user first', providing a clear usage guideline. It implies when to use this tool (remove a single topic) versus alternatives like replace_topics for bulk operations, though not explicitly stated.

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