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

No annotations provided, so description carries full burden. It describes the analysis process but does not explicitly state read-only nature or any side effects. Assumptions about input data (e.g., positive gross sales) are not clarified.

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 sentence, concise, front-loaded with main action. Uses arrows to show flow. No waste.

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 6 parameters, no output schema, and no annotations, description is fairly complete but lacks detail on output format (how 'flag' is presented) and edge cases. Could be more helpful with explicit output description.

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 description coverage is 0%. Description provides context for parameters by mentioning 'gross', 'deductions', 'expected', and 'actual_deposit', but individual parameters like 'processing_fees' and 'other_deductions' are not explained in detail. Baseline 3 because description adds some value but not complete parameter documentation.

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 the tool's purpose: to explain why a payout is less than sales by walking through gross, deductions, expected, and flagging gap if actual deposit given. It uses specific verbs and resource, distinguishing it clearly from sibling validation tools.

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?

Implicitly tells when to use (when needing payout discrepancy analysis). No explicit when-not-to or alternatives, but siblings are mostly validation tools, so context is clear. Slight deduct for lack of explicit guidance.

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