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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds useful context about id reuse and the connector's case list, but it doesn't disclose ordering, pagination, or potential size/volume behavior. This is acceptable given the annotations, but not a rich behavioral disclosure.

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 tightly written sentences: the first leads with the action and output fields, the second gives actionable downstream routing. Every clause earns its place, with no repetition of schema or annotation information.

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 zero-parameter, read-only, idempotent tool with an output schema, the description covers the essential invocation and data-retrieval context. It also provides the crucial integration detail that page ids from search name their case. Nothing required to call the tool correctly appears to be 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?

This tool takes zero parameters and the schema is empty, so there are no parameter details to explain. The description sensibly avoids inventing parameters and instead clarifies that the returned id is the `case` parameter for sibling tools, which is helpful cross-tool semantics. Baseline 4 is appropriate for a zero-parameter tool.

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 uses a specific verb ('List') and identifies the exact resource ('court cases this connector holds'), while enumerating the returned fields (id, caption, cause number, court, status, incident). It also differentiates itself from sibling tools by explaining how its returned id feeds into search, get_case_overview, list_case_topics, and list_record_limitations.

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 clearly establishes the context: call this tool to enumerate all cases held by the connector and obtain reusable ids. It explicitly documents how the id should be passed as the `case` parameter to sibling tools and notes that every page id from search names its case. It stops short of a full 5 because it doesn't explicitly state when not to use list_cases or directly contrast it with alternatives.

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