register_commands

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

The description implies a destructive write operation by stating 'Replace all', but it does not explicitly disclose that existing commands are overwritten or deleted. No annotations are present to cover this gap, but the action is understandable.

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?

Single sentence that is direct and to the point. No extraneous words.

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 tool with no output schema and no annotations, the description is too brief. It does not mention that all existing commands are replaced, any delay or effect, required permissions, or how to handle errors. Missing important context for the agent to use it safely.

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 description adds minimal value. The optional 'project' parameter is described in the schema, and 'commands' is defined as an array. The description does not provide additional semantic context beyond 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?

Description clearly states the action ('Replace all registered Discord slash commands') and the target ('current Top.gg bot project'). It is unambiguous and distinct from sibling tools, which are about votes, announcements, and project details.

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?

No guidance on when to use this tool versus others, no context about prerequisites (e.g., needing an existing bot project or token configuration), and no mention of when not to use it.

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