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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real behavioral context: the api:read scope requirement, the default page size of 100, that the response carries app_url, and the important caveat that latest_observation/why_now is 'attention, not verified evidence'. The monitoring freshness fields (monitor_last_checked_at, status enum including 'degraded') further signal staleness behavior. It does not discuss rate limits or ordering of results.

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?

Purpose is front-loaded in the first clause, which is good, but the body is one enormous semicolon-and-slash-delimited run-on enumerating roughly twenty fields. Because no output schema exists, the field dictionary does earn its place, but the density makes it hard to scan and a bulleted or grouped structure would carry the same information far better.

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 only two optional parameters, no output schema, and 0% schema description coverage, this description is the sole source of return-shape information and it delivers: field-by-field meanings, enum values, nested judgment structure, auth requirement, and pagination. Nothing an agent needs to decide to call it or interpret the result is missing.

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 0%, so the description must carry parameter meaning, and it does: limit is given range and a default of 100 that the schema does not state, and offset is identified as the pagination counterpart. Offset semantics beyond 'paginate' (e.g., ordering, whether it is row- or page-based) are left unstated.

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 the resource precisely and scopes it to the API key's own user ('YOUR Gambits'), which distinguishes it from any account-wide listing. It also names the sibling it feeds into ('pass it as case_id to get_gambit / get_gambit_history'), implicitly separating list-from-detail. It never explicitly contrasts itself with get_gambit or list_mandates, so it stops short of a 5.

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 'id (pass it as case_id to get_gambit / get_gambit_history)' instruction gives a concrete follow-up workflow, and 'Requires api:read' states a prerequisite. Pagination guidance ('limit (1-100, default 100) and offset') tells the agent how to page. No explicit when-not-to-use or alternative-listing guidance, so 4 rather than 5.

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