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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write nature is already conveyed, but the description adds meaningful operational context: a hard cap of 5 tickets per day to prevent accidental duplicates. That rate limit is not derivable from the annotations or schema, so it earns credit.

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?

Two compact sentences with no waste: the action is front-loaded and the rate-limit caveat follows. Every clause earns its place.

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?

With annotations covering the mutation safety profile, a fully documented 2-parameter schema, and no output schema required, the description only needs to clarify purpose and constraints. It does so adequately, though it omits what the created ticket returns (e.g., ticket ID).

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% and both parameters (subject, message) are already documented in the schema. The description adds no syntax, format, or length constraints for these fields, so the baseline 3 applies.

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?

States a specific verb+resource combination ('Eröffnet ein neues Support-Ticket'), which clearly distinguishes it from siblings like close_support_ticket and reply_to_ticket by implication. It does not explicitly name those siblings, so it falls short of a 5.

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 gives no explicit guidance on when to create a ticket versus closing, replying, or listing tickets. The rate-limit note implies caution but does not tell the agent which condition selects this tool over its siblings.

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