Put up the Add ticket button

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

With no annotations provided, the description carries the full burden. It discloses the key side effect ('Posting it again takes the previous one down rather than leaving two') and explains what happens when someone clicks the button. Minor gaps remain around permissions or error states, but the most important behavioral traits are covered.

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 four sentences, front-loaded with the purpose, then covering the click flow, alternatives, and idempotency. Every sentence earns its place; there is no redundant or filler content.

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 simple 3-parameter tool with no output schema, this description is complete: it covers behavior, side effects, alternatives, and defaults. The schema provides full parameter details, and the description adds the necessary operational context for correct use.

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%, and each parameter already has a clear description in the schema. The main description adds context about the overall workflow but does not significantly enhance parameter understanding beyond what the schema provides, so the 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 opens with a specific verb+resource: 'Post a game's standing "Add ticket" button in its channel.' It clearly distinguishes from siblings by naming create_channel and link_channel as tools that already do this during initial setup, and positions this tool as the way to restore or relocate the button.

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?

Explicitly states when to use the tool: 'for putting the button back after it has scrolled out of sight, or moving it somewhere else.' It also names create_channel and link_channel as alternatives that already perform this behavior, giving the agent clear guidance on 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.