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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds valuable behavioral details: includes test cases flagged with isTestCase, lists lifecycle statuses and sortable fields, and notes pagination. No contradiction with annotations.

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?

Well-structured with main purpose first, then details. A bit verbose with repeated status/sort lists, but each sentence adds value. Could be slightly shorter, but not wasteful.

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 output schema, description compensates by stating return fields ('reference, debtor name + country, amounts, lifecycle, partner, key dates'), pagination defaults, test case behavior, and filtering options. Fully adequate for agent understanding.

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 description repeats parameter info without adding new meaning. However, it reinforces the sort format and lists enum values, which is helpful but not essential. Baseline 3 is appropriate.

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?

Clearly states 'list the creditor's debt collection cases with pagination, status filtering, and sorting' directly after the title. The verb 'list' and resource 'cases' are specific, and it distinguishes from sibling 'get_case' by noting 'Use get_case for full detail on a specific case.'

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?

Provides explicit alternative: 'Use get_case for full detail on a specific case.' Also implies context of listing vs. detail, but does not explicitly state when not to use (e.g., for bulk operations) or other alternatives. Still clear and helpful.

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