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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description still adds meaningful context: an unknown ID returns an isError response, and IDs are never reused. It also discloses the shape of the returned data, including that superseded versions retain their reason and correction source.

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?

Front-loaded with the core action and purpose, then the payload. The long mid-sentence enumeration of returned fields is heavier than needed, especially since an output schema exists, but the closing error/ID-reuse sentence earns its place.

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 single-parameter lookup with a full output schema and complete annotations, the description covers purpose, input format, error behavior, and data semantics. Nothing an agent needs in order to call it correctly is missing.

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 100% with a pattern and example, and the description's 'Record IDs look like SX-07-A-0001' largely repeats the schema example. The only added semantic is that unknown IDs error out and are never reused, which is useful but not parameter-level detail.

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?

States a specific verb and resource: 'Fetch one Seraphix public record by ID.' The 'one ... record' framing clearly distinguishes it from siblings like search_records and get_filings_wire, and the enumerated payload confirms it is the single-record detail tool.

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?

Usage context is clear: exact-ID lookup for citing/checking a record, with the ID format spelled out. It stops short of naming alternatives (e.g., use search_records to find an ID first) or stating when-not to use it, so it is strong but not fully routed.

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