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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered structurally. The description adds nothing beyond that: no note on pagination, filtering behavior of the free-form 'query' object, error semantics for an unknown runId, or whether records are paged.

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 description is short but not concise in any useful sense: the identical sentence appears twice, and an opaque 'Operation ID: fab4996b...' is included that gives an agent no actionable information. Front-loading is a route string rather than an action statement.

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 nested-object parameter with 0% schema coverage, no output schema, and heavy sibling ambiguity means the description should carry real weight, yet it only echoes the endpoint. An agent could call it, but with no idea of what the 'query' object accepts or how results are shaped.

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% and there are two parameters, one of which ('query') is a free-form object with additionalProperties and no documented keys at all. The description must compensate but provides none of that: nothing about runId format, nor which query fields (status, limit, offset, cursor) are accepted.

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 only repeats the raw route 'GET /api/asc842-reconciliation/runs/:runId/records' twice; the verb+resource can be inferred from the URL but is never stated in words (e.g. 'list reconciliation records belonging to a run'). Several siblings (get_asc842_reconciliation_records_by_re_*, two other runs_by_runId tools, get_asc842_reconciliation_runs_*) are not differentiated at all, so an agent cannot tell them apart from this text.

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 use this tool versus the record-level sibling or the other runs_by_runId operations. The only directional hint is 'describe_operation provides native request schemas', which points at another tool for schema lookup, not at when this operation is the right choice.

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