approval_request_get_by_parameters

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

Discloses key behaviors: required statusId, error on missing, base64 encoding of requestorReason. Without annotations, description carries burden. Could mention pagination but core behaviors 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?

Single dense paragraph, front-loaded with purpose and critical note. Every sentence adds value without 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?

Given no output schema, description explains return value format (base64) and error condition. Suggests follow-up for richer context. Missing details on pagination but schema covers parameters.

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 coverage of top-level parameters is 100% but nested parameters lack descriptions. Description adds critical meaning for statusId (required, example for Pending) and base64 encoding, compensating for schema gaps.

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 'Approval Request: Get By Parameters' with specific verb and resource. It distinguishes from siblings by noting the required statusId and suggesting a follow-up tool for richer context.

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 statusId is required, warns about HTTP 500 if omitted, explains base64 encoding, and recommends alternative tool for decoded reason and richer context.

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