Create Asset (Snipe-IT)

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

Description states write operation and access requirement. Annotations indicate non-read-only, non-destructive, non-idempotent, open-world. No contradictions; description adds value beyond annotations.

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 sentences impart essential information with no wasted words. Front-loaded with core purpose.

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 minimum fields and access, but missing return value info. For a creation tool, describing the response (e.g., asset ID) would enhance completeness.

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 coverage is 100% but schema is vague (single payload object). Description compensates by specifying key fields (model_id, status_id, asset_tag) that are implicitly required.

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?

Title and description clearly state 'Create a hardware asset' with specific verb and resource. Distinguishes from siblings like snipeit_update_asset and snipeit_list_assets.

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?

Provides minimum required fields (model_id, status_id, optional asset_tag) and access requirement (write access). Lacks explicit when-not-to-use but context suffices.

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