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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the underlying endpoint (GET /subscriptions), which is mildly useful, but says nothing about pagination behavior, result volume, or default filtering (status defaults to 'active'), which the schema hints at but is worth surfacing.

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?

Two short clauses, front-loaded with the operation and filters, followed by the endpoint. Nearly zero waste, though the endpoint tagline is marginal value.

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?

For a five-parameter filtered list with no output schema, the description is adequate but thin: it omits pagination defaults, the 'active' status default, and any routing against the near-identical sibling tool. Nothing is misleading, but an agent still has open questions.

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 100%, so all five parameters already carry their own descriptions. The description restates the filter dimensions (customer, plan, status) but adds no format or default detail beyond the schema, 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?

Clear verb+resource: lists subscriptions with optional filters. It uses 'subscriptions' consistently with the name. However it does not differentiate itself from the sibling lago_list_customer_subscriptions, which is clearly a narrower read of the same resource.

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 implies when the tool is used (browse all subscriptions with optional filters) but gives no explicit when/when-not guidance or named alternatives, despite a very close sibling (lago_list_customer_subscriptions) that an agent would need help choosing between.

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