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

Description discloses state-changing behavior ('hides the pending suggestion until the specified date/time') and mentions an authorization requirement ('after authorization'), adding behavioral details beyond the annotations.

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?

Description is concise, front-loaded with the primary use case, and flows logically from purpose to state change to required inputs.

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 two-parameter tool with no output schema, the description provides sufficient context: purpose, state-changing effect, authorization requirement, and parameter sourcing.

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 descriptions already cover both parameters (suggestion_id and until) with clear meaning; description adds only a slight reinforcement ('Requires suggestion_id from list-space-suggestions and an until timestamp') without introducing new semantic information.

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 tool's purpose with a specific verb ('snooze') and resource ('space suggestion'), and distinguishes from siblings by noting it handles a single suggestion (not bulk) and specifically targets 'Autopilot/repository-sync documentation suggestion'.

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?

Provides explicit usage conditions ('when the user wants to postpone, remind later, or snooze one...') and parameter requirements, but does not explicitly contrast with alternative sibling tools like apply or discard, though context implies this tool is for temporarily hiding rather than finalizing.

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