faxdrop_get_fax_status

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

Discloses side effects (API hit, rate limits, caching), terminal statuses, and aligns with annotations (readOnlyHint, openWorldHint). No contradiction.

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?

Concise yet thorough, with clear sections (USE WHEN, DO NOT USE, SIDE EFFECTS, POLLING STRATEGY). No wasted words.

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?

Without output schema, description explains return values (status object + _cached flag). Covers all necessary context for a polling tool.

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 covers 100% of params; description adds context that faxId comes from faxdrop_send_fax, aiding correct usage.

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 'Check the delivery status of a previously sent fax.' It distinguishes from siblings by specifying it polls for faxes sent via faxdrop_send_fax.

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 provides when to use (polling for fax sent via this MCP), when not to use (faxes sent outside), and includes a detailed polling strategy.

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