request_approve

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

With no annotations, the description discloses SCA requirements, inline polling, fallback to pending response, and two-step flow via sca_session_token. It covers key behavioral traits beyond basic purpose.

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, each purposeful: first states purpose, second explains SCA flow. No wasted words, front-loaded with essential information.

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 SCA handling, polling, and continuation flow. Lacks explicit return value description, but no output schema exists. Adequate for the tool's complexity.

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?

The description adds significant meaning beyond the input schema, explaining the behavior of wait (polling, default 30, fallback) and sca_session_token (no polling, single execution). Schema coverage is 100%, but description enhances understanding.

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 tool approves a pending request, and the sibling list includes request_decline, distinguishing it. The verb 'approve' and resource 'pending request' are specific.

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?

The description explains SCA handling, polling defaults, and fallback to pending response, providing clear guidance on when and how to use. It does not explicitly exclude other tools, but the context is sufficient.

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