list_contracts

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without mentioning read-only nature, pagination, potential side effects, or required permissions. For a list operation, this lack of detail is a notable gap.

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?

The description is a single, front-loaded sentence with zero wasted words. It is highly concise and appropriately sized for a simple list operation, matching the standard of efficient communication.

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 the absence of annotations and output schema, the description should provide more context about return values, pagination, or usage constraints. It fails to do so, leaving the tool under-specified for an agent to invoke confidently. A list operation with filters deserves at least some behavioral or contextual detail.

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 describes 'status' and 'thirdparty_id' but leaves 'limit' undocumented (67% coverage). The tool description adds no parameter context, failing to clarify what 'limit' controls or how filters relate to the listing. The description does not compensate for the missing schema detail.

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 uses the specific verb 'Lister' (to list) and clearly identifies the resource as 'contrats/abonnements clients' (client contracts/subscriptions). This distinguishes it from sibling tools like list_projects or list_orders, making the purpose immediately clear.

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 no guidance on when to use this tool versus alternatives, nor does it mention any filters, prerequisites, or exclusions. It simply restates the action, leaving the agent without context on appropriate usage scenarios.

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