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

Annotations already declare idempotentHint=true, readOnlyHint=false, openWorldHint=false, and destructiveHint=true, so the safety profile is covered. The description adds genuine context by bounding the mutation to a rename only, though it does not note that the previous name is replaced (the destructive aspect) or any auth prerequisite implied by 'owned by the signed-in user'.

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?

Two sentences, zero waste: scope first, routing second. Every clause earns its place and the most important constraint is front-loaded.

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 two-parameter mutation with full schema coverage, complete annotations, and an output schema, nothing the agent needs is missing; the description complements rather than repeats the structured fields.

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%, with 'id' sourced from list_stream_decks and 'name' documented as trimmed and non-unique, so the schema carries the parameter burden. The description adds no format or constraint detail beyond that, so baseline 3 applies.

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?

States a specific verb (Rename) and resource (an existing stream deck) plus ownership scope (owned by the signed-in user) and explicitly bounds the effect ('nothing else changes'). An agent can distinguish it from create_stream_deck, update_stream, and reorder_stream_decks without opening any schema.

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 routes to alternatives with their conditions: reorder_stream_decks to move it, delete_stream_deck to remove it. This is the exact when-to-use/when-not pattern, leaving nothing to inference.

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