Create Entity (Snipe-IT)

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

Annotations already indicate write operation (readOnlyHint=false) and non-destructive. Description adds 'Requires write access', confirming permission need. No details on idempotency, error handling, or specific behavioral traits beyond what annotations provide. Minimal extra value.

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: one sentence listing entity types plus 'Requires write access'. No fluff, front-loaded with purpose. Every word earns its place.

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 is complex (multiple entity types, nested payload, no output schema). Description lacks explanation of return values, payload construction guidance, or error scenarios. Incomplete 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?

Input schema has 100% description coverage, so baseline is 3. Description does not add parameter details beyond the schema; it only lists example entity types already in schema. No guidance on payload structure.

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 clearly states verb (Create) and resource (non-asset entity) with examples, and distinguishes from sibling tool snipeit_create_asset by specifying 'non-asset'. This provides precise purpose and differentiation.

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?

While not explicitly stating alternatives, the description's phrase 'non-asset entity' and the schema's entity enumeration (with note that assets have their own tools) implicitly guide agents to use this tool for non-asset creation. 'Requires write access' gives a prerequisite. Could be improved with explicit when-to-use.

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