List sevDesk API operations

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

Describes a read-only search operation with no side effects. Lists available tags and number of operations. Lacks explicit non-destructive statement but context is clear.

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?

Concise, front-loaded sentences with no redundancy. Every sentence adds value (purpose, usage, tags).

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?

Complete for a catalogue search tool: explains what it returns, how to use it, and lists all tags. Output schema not needed as return structure is implied.

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?

All 4 parameters are described in the schema (100% coverage). The description adds details like free-text search scope and default limit, enhancing utility beyond 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 clearly states the tool searches the sevDesk API catalogue to find operationIds for non-dedicated tools, differentiating it from sibling tools that handle specific 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?

Explicitly tells when to use ('for anything not covered by a dedicated tool') and outlines the workflow: find operationId, then use describe_operation and call.

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