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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description reinforces this with 'GET /invoices' and hints at searchable invoice data, but it does not add details about auth, rate limits, or response behavior.

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 compact sentence plus the HTTP endpoint. It is front-loaded, waste-free, and easy to scan.

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 simple read-only list tool with full schema descriptions and strong annotations, the description supplies the operation, endpoint, and some field context. It could be more complete by distinguishing this from fieldpulse_get_invoice or clarifying that search is free-text, but it is broadly sufficient.

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 page, limit, search, sort_by, and sort_dir are already documented in the input schema. The description adds some context about invoice fields that may be searchable, but it does not clarify parameter behavior beyond the schema.

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 states a specific verb and resource: 'List or search invoices,' and adds the relevant invoice domains in parentheses. It is clear what the tool does, but it does not explicitly distinguish it from the sibling fieldpulse_get_invoice or from other list tools.

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 'List or search invoices,' but the description gives no explicit when-to-use guidance, prerequisites, or alternatives such as fieldpulse_get_invoice. An agent can infer the basic use case but must decide sibling selection on its own.

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