list_cases

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

No annotations are provided, but the description discloses that it returns metadata only (not full details) and includes a url for direct access. Since it's a read operation, it appropriately avoids side-effect claims. However, it does not mention authentication or rate limits.

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 a single sentence that is front-loaded and concise. Every part is meaningful: it states the action, the scope, the content, and an instruction to expose the url.

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 parameters and no output schema, the description is complete. It specifies the scope ('current user'), the return type (metadata only), the fields, and an actionable instruction for the agent (expose url).

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?

There are no parameters, and schema coverage is 100%. The description adds value by detailing the output structure (id, name, occurrence, location, summary, counts, url) beyond what an empty schema provides.

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 clearly states it returns the current user's case list (metadata only) and enumerates the fields (id, name, occurrence, location, summary, counts, url). It distinguishes from siblings like get_case_detail by specifying 'metadata only'.

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 specifies it's for listing cases and provides context about the output. It does not explicitly state when not to use it or name alternatives, but from sibling tool names (create_case, delete_case, get_case_detail), the usage is implied.

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