List contacts

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

The description mentions 'Read-only,' which is a behavioral trait, but no annotations are provided to supplement this. It does not disclose pagination behavior, default limit, sorting, or error handling, which are important for a list operation with no output schema.

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 extremely concise—two short sentences that convey the essential purpose and a behavioral trait. No unnecessary words, making it easy to process quickly.

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 an output schema and annotations, the description should provide more context about return values, pagination, or filtering behavior. It only states listing of customers and suppliers, leaving the agent uncertain about what data is returned and how the 'limit' and 'search' parameters affect results.

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% (both 'limit' and 'search' have descriptions). The tool description does not add meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 states the specific verb 'list' and the resource 'contacts' (customers and suppliers). It distinguishes this tool from sibling tools like sevdesk_list_vouchers and sevdesk_list_invoices, which handle different resources.

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 implicitly indicates the tool is for listing contacts, but it provides no explicit guidance on when to use it versus alternatives, nor any prerequisites or exclusions. The context of sibling tools shows many list operations, but no differentiation is offered.

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