create_ticket

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

No annotations provided; description is only one line with no behavioral disclosure. It does not state side effects, permissions, or whether the operation is destructive. The mismatch with the schema further impairs transparency.

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?

Extremely concise (single sentence), but the content is insufficient. While brevity is positive, the lack of structure (no bullet points, no front-loaded details) reduces usefulness.

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 complex nested schema (required cart_lines and payments), the description is completely inadequate. No output schema, no annotations, and no explanation of return values or side effects. The agent cannot safely use this tool based on the current description.

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?

The input schema has 100% coverage of parameters but lacks descriptions for individual fields (e.g., cart_lines, payments). The description adds no meaning beyond the schema, leaving the agent to infer usage from field names and types alone.

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?

Description is a tautology ('Créer un ticket IT' = 'Create an IT ticket') and contradicts the input schema which requires cart_lines and payments, suggesting a sales transaction rather than an IT support ticket. This misleads the agent about the tool's actual function.

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?

No guidance on when to use this tool versus siblings like create_order, create_invoice, or create_quote. The description does not mention prerequisites, alternatives, or context for usage.

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