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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: the call costs $0.02 and requires an X-PAYMENT header. However it never states whether this is a mutation, whether a failure record is immutable, what receipt_id must reference, or what happens if payment is missing.

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?

One short sentence with no waste and the price is front-loaded, but the brevity comes at the cost of the disambiguation the tool actually needs. It is under-specified rather than efficiently compact.

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?

A two-parameter paid write operation with no annotations, no output schema, and zero schema documentation needs the description to explain payment flow, receipt linkage, and result behavior; none of that is present, and the name/description mismatch adds unresolved ambiguity.

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?

Both parameters (reason, receipt_id) have 0% schema description coverage and the description says nothing about them. Whether receipt_id refers to the X-PAYMENT receipt or a prior dispense record is completely undetermined, so the description fails to compensate for the coverage gap.

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 says 'File a step-therapy prior-auth record', a concrete verb+resource, but the tool is named formulary_report_failure, which implies reporting a failed claim/PA, not filing a new PA record. An agent reading both cannot tell which action is actually performed, and no sibling is named to disambiguate.

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?

There is no when-to-use or when-not guidance, and none of the siblings (formulary_file_daw, formulary_verify_receipt, formulary_dispense) are referenced to route the agent between filing a PA, reporting a failure, and verifying a receipt. Usage is at best implied by the verb 'File'.

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