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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the scoping constraint 'available to the connected organization' and hints at the search behavior, which are not in the annotations. No contradiction; it adds modest value beyond the structured data.

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 sentences with no fluff. The purpose is front-loaded, and the usage hint is a natural follow-on. Every word earns its place.

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?

An output schema exists, so return format is covered. The description covers the core purpose and a workflow. Pagination details (cursor behavior) are in the schema, so not missing. Minor gap: no mention of the org-scoping beyond the phrase, but that is already stated.

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?

The schema already documents cursor and search with detailed descriptions, covering 67% of parameters. The description adds intent for the search parameter ('resolve a case by title') but does not address limit or cursor beyond the schema. Since coverage is moderate, the description does not fully compensate but adds some value.

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 the tool lists or searches call cases, which is a specific verb+resource. It distinguishes itself from list_calls (calls vs cases) and get_case (single vs collection), and even ties it to a workflow (resolving a case before creating a call).

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 provides a concrete usage scenario: 'Use search to resolve a case by title before creating a call.' This implies when to use the tool, but it does not explicitly contrast with alternatives like get_case for a known case ID. It gives a clear context without exclusions.

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