Create Service Request (guided)

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

With no annotations, description fully discloses the multi-step workflow: customer lookup/creation, then request creation. It explains the conditional logic for company creation. Missing minor edge cases but adequate.

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 with purpose, and contains no filler. Every sentence adds value and is efficiently structured.

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?

Tool has moderate complexity with 5 params, no output schema. Description covers key behaviors and workflow. Could elaborate on error handling or return format, but still provides enough for effective use.

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?

Description adds value beyond schema by explaining how 'customer_name' is used for matching and the role of 'create_if_missing'. Other parameters are sufficiently described in schema (60% coverage), and description provides context for the overall flow.

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 performs end-to-end intake: find/create customer, file a Request, and return summary. It distinguishes from sibling 'create_request' by specifying when to use this over the raw tool.

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 explains when to use: starting from customer name rather than ID. Provides detailed behavior on company matching and creation with 'create_if_missing' parameter.

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