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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), but the description adds genuine behavioral context not present in structured fields: link confidence semantics ('confirmed' shared RIN vs 'probable' shared docket) and the data-integrity rule that missing stages are never fabricated. That is real value beyond annotations.

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?

Two dense sentences that front-load the returned lifecycle before the input guidance. Nearly every clause earns its place, though the stage enumeration is slightly list-heavy.

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, so the description carries the burden of explaining returns; it does so at a medium level (lifecycle stages, observed events, deadline history, link confidence) but omits response shape, pagination, and the behavior when no identifier is given despite zero required parameters.

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 only 33% (only document_number is documented), so the description must compensate. It names all three accepted identifiers, signaling they are alternatives, but adds no format or precedence guidance for rin/rulemaking_id and does not resolve what happens when none of the zero required parameters is supplied.

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 resource (the lifecycle of a rulemaking) and enumerates the stages returned — proposed rule, comment periods, final rule, effective date, corrections, withdrawals. It is clearly distinguishable from a single-document fetch, though it never explicitly contrasts itself with siblings like get_regulatory_document or get_regulatory_deadlines.

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 tells the agent how to invoke the tool ('Give a RIN, a rulemaking_id or a document_number') but never says when to choose this tool over get_regulatory_document or get_regulatory_deadlines, which cover overlapping ground. Usage is implied by the topic rather than stated.

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