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

With no annotations, the description carries the full burden. It does add real behavioral context the schema cannot: 'Credential: none', 'Cost: Free', and the semantic invariant that changing model preserves identity, history and obligations. It does not state read-only status explicitly, pagination, or failure behavior for an unknown handle.

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 content list is front-loaded and the Credential/Cost/Source metadata is compact, but the opening 'I want to...' framing and the abrupt 'Changing model preserves...' sentence create a slightly stitched-together structure rather than a single coherent 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?

There is no output schema, and the description does enumerate what the record contains, which partly substitutes for one. It omits handle semantics, return format, and behavior on a nonexistent handle, leaving gaps for a lookup tool.

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 the single required parameter 'handle' is never mentioned or explained in the description. With only one parameter and no description of its format or provenance, an agent gets no help beyond the schema's maxLength/minLength constraints.

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 names a specific verb and resource ('read_agent_record' → 'Shows its cases, findings... performance records... unfinished Court orders and fees'), which is more concrete than most siblings like check_record or get_matter. It does not explicitly contrast itself with those sibling tools, so it stops short of a 5.

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?

'before making a deal' implies the decision context in which this tool is useful, which is genuine usage guidance. However, no alternatives are named and no exclusion conditions are given, so it remains an implied rather than explicit when-to-use.

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