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

Annotations already declare readOnly, openWorld, and non-destructive behavior. The description adds the API endpoint (GET /financial/list-invoice) and labels the data as 'Financial data', which suggests sensitivity, but gives no further behavioral context like pagination, rate limits, or return format.

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 front-loaded with the core purpose and returned fields, then lists optional filters. It is concise overall, though the fragment 'Financial data.' is slightly redundant and the structure is a bit choppy.

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 list tool with 6 parameters and no output schema, the description adequately covers the returned fields and optional filters. It omits details like pagination or sorting, but given the simplicity and existing annotations, it is sufficiently complete for an agent to invoke correctly.

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 67% with some properties lacking descriptions (invoice_id, appointment_id). The description adds that unit, invoice, and appointment are optional filters, but does not explain their semantics beyond that, leaving a gap for the undocumented parameters.

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 clearly identifies the resource (financial invoices) and scope (date range, receivables vs payables) with specific returned fields. It lacks an explicit verb like 'list' in the description itself, but the title and overall phrasing make the purpose unambiguous.

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 implied by the date range and direction parameters, and the optional filters are mentioned. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives—though no direct sibling tool exists for invoices.

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