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

While annotations already indicate readOnly, idempotent, and non-destructive behavior, the description adds critical behavioral context beyond annotations: matter_uid is opaque and sometimes mislabelled, verification and link_status have current caveats, private individuals are withheld by policy, and chains_sampled affects interpretation. The 'Data by AI Law Tracker' and 'not legal advice' statements add further transparency.

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 description is fully detailed yet every sentence earns its place: the main fetch action, the opaque-key warning, the field-reading cautions, the privacy caveat, the chains_sampled caveat, and the data/licensing note. No filler or redundancy; key warnings are clearly placed after the core usage.

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?

Given no output schema and a single param, the description does an exceptional job of covering both the input and the expected output semantics: it enumerates the components of the full chain and pre-indicates how to interpret specific fields. It also warns about common confusions and privacy filtering, making it nearly self-contained for safe invocation and result interpretation.

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 already documents matter_uid as from a search result, but the description adds essential semantic cautions: the uid is opaque, not a description, and should not be read for the matter name; placeholders or the `caption` field should be used instead. This significantly improves param understanding beyond the raw schema.

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 leads with a specific verb and resource: 'Fetch one enforcement matter by its matter_uid' and explicitly enumerates the full chain it returns (timeline, parties, relief, statutes, source documents). It clearly distinguishes this from its sibling search_enforcement_matters by framing matter_uid as coming from search and by listing the richer detail returned.

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 implicitly defines when to use the tool: after a search_enforcement_matters result provides matter_uid, to obtain full matter detail. It does not explicitly name alternatives or exclusions, but the workflow context is clear. The informational-only language also signals not to use it for authoritative legal conclusions.

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