Submit Catalog Request

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

Discloses that the tool creates a real service request, which is critical behavioral info. Explains variable value format and reference fields. With no annotations, the description provides key behavioral context, though could mention side effects like approval triggers.

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 succinct sentences front-load the core purpose and output, followed by a focused IMPORTANT clause. No redundant information.

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?

Covers key aspects: purpose, return values, prerequisite tool, and variable formatting. Lacks detail on error handling or idempotency, but is adequate given the presence of a prerequisite reference.

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%. The description adds value by clarifying variable value format (key-value object with strings) and handling of reference-type variables, which is not fully detailed in the schema. Also notes the returned REQ and RITM numbers, partially addressing outputs.

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 submits a service catalog request via the ServiceNow order_now API and returns REQ and RITM numbers. It distinguishes itself from sibling tools like list_catalog_item_variables.

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 advises to first use list_catalog_item_variables to understand required variables. Notes that it creates a real request, but does not compare to alternative tools or state when not to use it.

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