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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the bar is lower, and the description adds real value beyond them: newest-first ordering and the exact meaning of openOnly ('still open (not Closed)'). The trailing 'Read-only' merely restates the annotation and the description says nothing about truncation or result-count behavior beyond limit.

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?

Front-loaded with purpose and return fields, then usage triggers, then the behavioral note — a sensible order with no wasted sentences. The four example queries are slightly padded but justified as routing aids for a conversational trigger like 'check on my open support ticket'.

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?

With no output schema, the description correctly compensates by listing the returned fields (number, subject, status, priority, opened date) and the ordering. It is nearly complete for a two-optional-param read tool; only the behavior when limit is omitted versus capped is unspecified, which the schema covers anyway.

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 both parameters are already documented in the schema, including the default 10/max 25 and the openOnly definition. The description restates the openOnly semantics without adding syntax or format detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb+resource ('Returns the customer's support tickets (Salesforce Cases)') and enumerates the returned fields, so an agent knows exactly what it gets. No sibling tool touches support cases, so there is no ambiguity with the hosting/DNS/lookup tools in the list.

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?

Gives an explicit trigger condition ('Use whenever the user asks about a support ticket or case') backed by four realistic user utterances, which is strong routing guidance. It stops short of naming exclusions or alternatives, though none of the sibling tools plausibly overlap.

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