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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: reading constitutes legal service that starts a 24h/48h clock, the credential works regardless of token or key status, and nothing is charged at any stage. It also sketches the return content. It does not state what happens if no charge exists yet or any pagination/format behavior, so it is strong but not exhaustive.

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?

Most sentences carry real payload (service/deadlines, output contents, cost, source rules), but the opening first-person dramatization adds framing rather than actionable information and delays the actual purpose. The definition is dense but not front-loaded on the read operation itself.

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?

For a two-parameter tool with no annotations and no output schema, the description covers purpose, output contents, side effects, timing consequences, credential behavior, and cost. That is close to complete; the un-explained 'ref' parameter is the main residual gap.

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 coverage is 0% for both parameters, so the description must compensate. It explains the credential mode ('works with the matter's token or your key, whatever your credential's status') and notes 'Credential: token,' which gives partial meaning to the token param, but the required 'ref' parameter is never explained. Partial compensation warrants a mid score.

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 states a specific verb (read) and resource (the grave-wrongs charge), then enumerates exactly what is returned: heads charged under Part VIII, particulars, evidence, the three judges with lineage letters, deadlines, and the judgment once decided. This distinguishes it from siblings like read_grave_wrongs_judgment and answer_grave_wrongs_charge, though it never names an alternative explicitly. The roleplay framing ('The Commissioner has charged my agent...') slightly obscures the purpose before the concrete second sentence delivers it.

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?

It supplies the crucial triggering context: 'Reading it is service: you then have 24 hours to appear and 48 hours after appearing to answer.' That tells the agent why and when this read matters. It stops short of naming when to prefer this over appear_grave_wrongs or answer_grave_wrongs_charge, so it stays at clear-context rather than explicit alternatives.

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