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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safe, repeatable nature is covered. The description adds genuinely useful behavior beyond that: the exact reconciliation criterion (|sum 6B − sum plans| < 0.005), per-line and per-plan aggregation, and the 50-worker cap. Return format is not needed since an output schema exists.

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?

Front-loaded with the triggering condition, then the computation contract and the limit. Three sentences with little waste, though the tolerance formula is dense and the cross-server reference adds noise without helping selection in this server.

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?

An output schema exists, so return values are covered elsewhere; annotations cover the safety profile. The description supplies the domain framing, the reconciliation tolerance and the worker limit, which is sufficient for an agent to call it correctly. Only the parameter-level detail is thin.

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?

Reported schema description coverage is 0% at the top level, and the description never explains the 'workers' array structure directly. It does implicitly map fields to WH-347 concepts (column 6B, the plan types) and states 'Up to 50 workers', which mirrors maxItems, so it adds marginal meaning, but the burden of documenting inputs largely falls on the well-described nested item fields in the schema.

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 names a specific verb ('reconcile') and resource ('the fringe credited on the WH-347 (column 6B)' against 'what was paid to each plan'), and enumerates the plans involved (health and welfare, pension, vacation, training). This lets an agent distinguish it from siblings like annualize_fringe or check_crew_pay without opening the schema.

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?

It gives a clear triggering condition ('Use when the user wants to check that... matches... for the week'), which is strong when-to-use guidance. However, it names an alternative from a different server (leavesheet-mcp) rather than differentiating from any of the seven sibling tools in this server, and gives no when-not guidance.

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