Register app command

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

The description discloses important non-obvious behaviors beyond the annotations: upsert semantics (update if name taken), propagation delays, daily rate limits, and the lack of support for subcommands/subcommand groups. This gives the agent essential context for expectations and side effects.

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 three concise sentences, front-loaded with the primary action. Each sentence adds meaningful information without fluff. It is cleanly structured and easy to scan.

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's moderate complexity (5 parameters, no output schema, write/update operation), the description covers the key usage considerations: upsert behavior, timing, rate limits, and unsupported features. It could mention what the response contains, but it is sufficiently complete for selection and invocation.

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. The description adds useful guidance for the guild parameter (pass it while iterating) and implies name semantics via the update-in-place behavior, which adds value beyond the schema definitions.

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 clearly states the verb and resource: 'Register a slash command', and adds the nuance that it updates in place if the name already exists. This distinguishes it from list_app_commands and delete_app_command, though it overlaps with update_app_command.

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?

It provides explicit context for when to use it, especially the guild vs global command trade-offs ('guild commands appear immediately, while global commands can take up to an hour... rate limited per day'). However, it does not explicitly mention alternative tools like update_app_command or when not to use this tool.

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