Create Satisfaction Survey

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

Annotations already indicate a write operation (readOnlyHint=false), and the description's 'Create' is consistent. The description adds the one-survey-per-ticket rule, which is beyond annotation scope, but it does not disclose error behavior or permissions, so it's a 3.

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 brief sentences capture purpose and constraint with zero waste. The description is front-loaded with the HTTP method and immediately states the core action.

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?

The definition is adequate for a creation tool with well-described parameters; the uniqueness constraint is important context. However, without an output schema, it could mention the response or conflict handling, keeping it at a 4.

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 9 parameters have descriptions in the schema, so baseline is 3. The description's uniqueness rule duplicates the ticket_id schema description, adding no new parameter semantics beyond what the schema already provides.

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 identifies the verb (Create) and resource (satisfaction survey), and the uniqueness constraint 'Only one survey is allowed per ticket' distinguishes it from sibling tools like get/list/update. The HTTP method adds precision.

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?

It states the action and the key constraint 'Only one survey is allowed per ticket,' giving clear context for when to use it. However, it does not explicitly mention alternatives or exclusions beyond the uniqueness rule, so it's a 4.

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