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

Annotations disclose the key profile: not read-only, not idempotent, not destructive, closed-world. The description adds nothing beyond that — notably it never explains why a 'check' is flagged as a non-read-only, non-idempotent operation (presumably it records an audit/decision event), what happens on repeat calls, or whether any authorization is required. With annotations present the bar is lower, but a mutating 'check' with undisclosed side effects is a meaningful gap.

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, front-loaded sentence with no filler, which is good. But it is under-specified rather than concise — the brevity comes at the cost of the information needed to invoke the tool.

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 one opaque request-body parameter, no output schema, and annotations indicating a non-read-only, non-idempotent operation, the description should carry far more: what the body contains, what a pass/fail looks like, and what side effect occurs. Instead it offers three ambiguous check types and no return semantics.

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?

There is a single parameter, 'body', and the schema's own description merely says 'See the AffixIO OpenAPI schema resource for the contract' — a pointer, not semantics. The tool description says nothing about the body shape, and unlike a normal high-coverage case the schema does not carry the weight here, so the agent is left with no usable parameter guidance.

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 verb is 'Check' and the resource is 'finance', but the object of the check is given as three loosely related alternatives (eligibility, spending limits, risk context), so an agent cannot tell what decision or value the tool actually produces. It is distinguishable from finance_catalogue/finance_market only by implication, not by any stated boundary. Minimum viable, but vague on what is actually being checked.

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 statement of when to call this versus the obvious siblings finance_catalogue or finance_market, no prerequisites, and no indication of what inputs the caller must already have. The description is a bare capability statement with no routing guidance.

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