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 covered. The description adds no behavioral context beyond the raw route — nothing about what a reconciliation run record contains, whether the runId must come from the list endpoint, or what happens on an unknown ID.

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 same route sentence is duplicated verbatim, and an internal operation ID (d0a816fb60007cd9d236b0dd) is surfaced with no explanation of how an agent would use it. The content is short but the duplication and internal identifier consume space without adding information.

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 no output schema, 0% parameter description coverage, and a nested 'query' object, the description carries the burden of explaining inputs and return shape — and it does neither. For a fetch-by-ID tool an agent needs at minimum what a 'reconciliation run' is and where runId comes from, neither of which is present.

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 (a required path param runId and an unexplained free-form 'query' object). The only semantic clue is the literal ':runId' placeholder in the route, which implies runId is a path identifier but not its format or source; the 'query' object is left completely undocumented.

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 restates the HTTP route 'GET /api/asc842-reconciliation/runs/:runId' twice; the name/title already contains that string, so it is effectively a tautology. An agent can infer this fetches an ASC 842 reconciliation run by ID, but the description never says so in plain language and gives no way to distinguish it from the many sibling tools with nearly identical names (e.g. get_asc842_reconciliation_runs_by_runId_646108e3..., _fab4996b...).

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 its near-duplicate siblings or the list endpoint get_asc842_reconciliation_runs_e4d8931a. The only indirect hint is that 'describe_operation provides native request schemas', which points at a companion tool for schema discovery but says nothing about selection criteria.

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