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

With readOnlyHint/idempotent already covering the safety profile, the description still adds real value: it discloses that the newest ESAC year is partial, that thin years are flagged in the response, and that DOJ does not publish the reason for Non-Compliant/Ineligible status. The interpretive guardrails (fiscal years must not be combined, controlled equipment is already in ESAC categories) prevent concrete misuse. It stops short of describing result counts, pagination, or response shape.

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 purpose is correctly front-loaded in sentence one, but the remainder is an unstructured run of caveats that blurs into the return-value list. Most caveats are specific and non-generic, yet the lack of grouping (what it returns vs. how to interpret it) makes the definition harder to scan than its length requires.

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 read-only lookup with no output schema, the description does the heavy lifting on return content (status, sharing labels, payments by federal FY, ESAC certifications by agency FY) and on interpretive pitfalls. Gaps remain around pagination/result-count behavior and what happens when the substring matches many agencies, but the essential information is present.

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%, so the schema already documents state, agency and limit. The description reinforces that agency accepts a name substring or an exact ORI, but adds no syntax or matching nuance beyond the schema and never mentions the limit parameter or its 1-25 cap.

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 first sentence gives a specific verb (find), a specific resource (DOJ equitable-sharing agencies), and the exact lookup keys (state/territory plus agency-name substring or ORI). It is clearly distinct from generic search tools, but it never distinguishes itself from close siblings like forfeiture_payments or doj_by_company, which an agent could easily confuse it with.

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?

The description explains what comes back but gives no when-to-use or when-not-to-use guidance, and no alternative is named. An agent cannot tell from this text whether to reach for this tool or forfeiture_payments when it wants payment-level data; the only implied guidance is the required state scoping.

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