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

The readOnlyHint=true annotation already establishes safety, and the description adds useful behavioral context: default summary fields are returned when 'fields' is omitted, and filtering uses ABRA Flexi's filter language with specific operators and date format. It does not discuss pagination, authentication, rate limits, or error behavior, so it is adequate but not rich.

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 purpose is front-loaded in the first clause, followed by relevant filter details. The long operator enumeration and evidence examples are somewhat dense, but they earn their place by clarifying a non-obvious query language.

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 six parameters, a large evidence enum, full schema description coverage, and a read-only annotation, the description covers the essential purpose and filtering behavior. It is slightly incomplete on sibling-tool routing and does not mention pagination, but pagination is documented in the schema.

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 100%, so the baseline is 3. The description adds meaning beyond the schema for the most complex parameter by documenting filter operators, like-similar behavior, begins/ends/between/in, and date format, plus the default return-field behavior.

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 records of any business evidence,' and gives examples of evidence types. It is clear what the tool does, but it does not explicitly distinguish itself from the many dedicated list_* sibling tools such as abraflexi_list_issued_invoices.

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 explains filtering syntax but gives no explicit guidance on when to use this generic tool versus the dedicated sibling tools, nor any exclusions. An agent must infer that this is the fallback/general listing tool.

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