Create Purchase

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

The description discloses that it adds a new row in NetBox and describes the return format (Markdown or JSON). This adds behavioral context beyond the annotations (readOnlyHint=false, etc.), but doesn't detail error cases or permission requirements.

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?

The description is concise, with two short paragraphs. It front-loads the purpose and then adds the dry-run advice and return info. No redundant sentences.

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 rich schema and annotations, the description provides sufficient context by explaining the return format and the dry-run recommendation. It doesn't cover all aspects of the tool (e.g., required fields are in schema), but it is complete enough for a CRUD tool.

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 high coverage (78%) with descriptions for most parameters. The description adds no extra parameter details beyond what the schema provides, so a baseline score of 3 is appropriate.

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 it creates a new purchase in NetBox, using specific verbs and the resource name. It distinguishes from sibling create tools for other resources.

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 advises to ask before calling if the user wanted a dry-run, which is a clear usage guideline. However, it does not explicitly state when not to use this tool or mention alternatives, though the context of many siblings implies this is for purchases.

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