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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description contributes nothing beyond that: no indication of what the 'status' payload represents, no auth/scope requirements, no note on what happens for a run in an invalid state.

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?

It is short, but the single sentence is duplicated verbatim, so half the text is pure waste. There is no front-loaded plain-language statement of purpose, just a raw HTTP path.

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 read tool with no output schema needs the description to say what comes back (run status, current stage, completion state). Here the description is functionally a generated route stub plus a pointer to describe_operation; an agent has no idea what the response looks like or how it differs from the four sibling run-status/run-detail tools.

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% across 2 parameters. The path template ':id' at least lets an agent map params.id to the journal close run identifier, which is the one piece of meaning added. The 'query' object (additionalProperties: {}) is left entirely unexplained in both schema and description.

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 is a restatement of the endpoint path 'GET /api/accounting/journal-close/runs/:id/status', from which an agent can infer it retrieves the status of a journal close run by ID. However, it never says so in plain language and does nothing to distinguish it from the several sibling tools named get_accounting_journal_close_runs_by_id_196eafa..., _3a80565..., _e033511..., which likely hit adjacent sub-resources of the same run.

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?

No statement of when to prefer this tool over the sibling journal-close run endpoints. The only routing hint is that 'describe_operation provides native request schemas', which points to a metadata tool, not to usage conditions or alternatives.

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