Manage topic access

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

The description goes well beyond the annotations by disclosing that removing access breaks running publishers, granting access exposes traffic, deny is the only way to carve exceptions from wildcard grants, and revoke restores broader rules. This aligns with destructiveHint=true and readOnlyHint=false, and no contradiction with annotations is present.

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 organized into four short paragraphs: purpose and prerequisites, destructive rationale, pattern/action semantics, and server restrictions. It is front-loaded with the core action, and each sentence adds operational value without meaningful padding.

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 destructive mutation tool with four parameters, a confirmation flow, wildcard constraints, and server-specific restrictions, the description covers all key invocation factors. The presence of an output schema means return-value documentation is already handled, so nothing essential is missing.

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 100%, so the baseline is 3, but the description adds meaningful context beyond the schema: it explains the wildcard pattern semantics, the practical difference between deny and revoke, and the NTFY_TOPICS restriction. It does not reach 5 because the raw parameter meanings are already well documented in 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?

The description opens with 'Sets or removes an account's access to a topic or topic pattern,' which is a specific verb plus resource and clearly distinguishes this mutation tool from the sibling check_topic_access. It also names the required admin and confirmation gate, so there is no ambiguity about what the tool does.

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 gives clear context for when to use the tool: it requires an admin account, is destructive in both directions, and is gated by a confirmation token. It also explains wildcard behavior and NTFY_TOPICS restrictions. However, it does not explicitly say 'use check_topic_access instead for read-only checks,' so it stops short of full when-to-use versus alternative guidance.

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