request_decline

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

Given no annotations, the description well covers SCA requirements, polling, and fallback behavior. However, it lacks details on return value structure and potential 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?

Two concise sentences efficiently convey purpose and key behavioral notes with no redundancy.

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?

Covers core action and SCA intricacies adequately for a decline tool, but missing output schema information and elaboration on 'declined_note' parameter slightly reduces completeness.

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?

With 100% schema coverage, the description adds value by explaining the 'wait' parameter's default and the 'sca_session_token' purpose beyond 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 'Decline a pending request' with a specific verb and resource. It also distinguishes from sibling 'request_approve' by defining the opposite action.

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 guidance on SCA handling and default polling behavior, but does not explicitly state when not to use it or compare to alternatives beyond SCA flow.

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