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

The annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuine context by disclosing the three content areas returned (work, cost, caller access), which hints at an authorization-scoped read. It stops short of saying what happens when the caller lacks access or whether cost data is delayed/aggregated.

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?

A single front-loaded sentence with no filler and the read verb first. It is tight, though its brevity comes partly from omitting necessary detail rather than from disciplined editing.

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 undocumented parameter and no output schema, the description carries a lot of weight and only partly discharges it — it sketches the return content but leaves the required argument unexplained. For a simple one-param read this is borderline adequate rather than complete.

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% for the single required 'find_id', and the description never mentions an identifier, its format, or where to obtain one. The only hint is the vague 'the finished work', which does not tell the agent that find_id selects the execution being read.

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 'Reads' plus a three-part object ('the finished work, what it cost, and the caller's access to its results') gives a rough sense of the payload, but it never names the resource the tool is actually about — a capacity execution — nor ties it to the 'find_id' identifier. Against siblings like get_capacity_balance, get_capacity_quote, and get_capacity_request, nothing here tells an agent which one to pick.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent is left to infer from the name alone that this is the post-hoc read of a completed run rather than a quote or balance lookup.

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