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

The description carries real behavioral content: it discloses that figures are earned/owed rather than paid and that settlement happens outside this tool. However, it asserts "Read-only" while the annotations declare readOnlyHint=false — a direct mismatch that forces the flag, even if the annotation is merely the MCP default being corrected.

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?

The definition is front-loaded with the ledger meaning, then units, then the parameter rule, then the safety note — no wasted clauses. The closing line ("what makes the clearinghouse fund restoration") is motivational rather than operational, but it is short.

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?

With an output schema present, the description need not enumerate return fields, and it covers purpose, parameter behavior, and the paid-vs-owed distinction. The only real gap is the read-only claim disagreeing with readOnlyHint=false.

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 is 0% and the schema never explains that an empty project_id means "all projects," so the description's "Pass a project_id for one project, else all" adds genuinely missing semantics. It stops short of describing the expected ID format.

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 defines the resource precisely as a supply-side disbursement ledger showing what each project has earned from retirements and is owed, naming the units (gross_proceeds_minor + retired_g). That is specific enough to separate it from settlement_batch or disbursement_schedule, though no sibling is named explicitly.

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?

"Pass a project_id for one project, else all" gives concrete invocation guidance, and "Read-only — the CEO settles the actual payout" effectively excludes the settlement use case and points the agent elsewhere. It does not name which sibling tool to use for payouts, so alternatives are only implied.

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