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

Annotations already declare readOnly, idempotent, closed-world, so the safety bar is lower; the description adds real value by defining all five status values, including the non-obvious 'orphaned' (ticket not found) and 'closed_unresolved' (Won't Do/Duplicate/Declined), and by naming the returned attributes and the REST endpoint it mirrors. It stops short of disclosing pagination, result limits, or behavior when no tracker is connected.

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?

Three sentences, each earning its place: what is listed, the status vocabulary, then the endpoint mapping last. The resource description is front-loaded and the enum glossary is compact rather than padded.

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 compensates by enumerating the returned attributes and decoding status values, which is enough to call and interpret the tool. Remaining gaps are secondary: pagination behavior, an empty-result story, and clarity on whether owner_user_id is a filter.

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 description coverage is 0%, so the description carries the burden: it thoroughly explains the status enum, which is the parameter most in need of definition. However, item_type and owner_user_id receive no explanation beyond the generic phrase 'Plutus-side owner', and it's unclear whether owner_user_id filters results or is merely a returned field.

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 and resource: lists tickets linked to savings recommendations and anomalies, plus the fields returned (tracker status, resolution, owner). That distinguishes it from list_savings_recommendations and list_anomalies, which return the underlying items rather than their tracker links, though the description never names those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the tool for cross-referencing tickets against recommendations/anomalies, and the status glossary hints at valid filter intents. There is no explicit when-to-use versus the recommendation/anomaly listing tools, and no note on prerequisites such as needing a synced tracker connection.

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