Snipe-IT raw request

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

Annotations already declare destructive, open-world, non-idempotent behavior, so the safety profile is covered. The description adds useful operational context: bearer auth, retry, status-envelope check, and pagination hint are automatic. It does not mention permission requirements or the confirm gate, though the schema documents confirm.

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 compact sentences with no waste. The escape-hatch purpose is front-loaded, followed immediately by the automatic handling details.

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?

For an open-world, destructive raw API tool, it covers purpose, usage condition, and automatic auth/retry/pagination behavior. The schema covers the destructive confirm parameter, though an explicit warning about write operations and permissions would improve 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%, with method, path, query, body, and confirm all documented in the schema. The description only restates path/method at a high level and adds no syntax, constraints, or examples beyond the schema, so baseline 3 applies.

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?

States a specific raw-request capability: executes ANY HTTP method against SNIPEIT_API_BASE{path}. The 'generic escape hatch' framing clearly distinguishes it from the many dedicated snipeit_* siblings.

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 says 'Use when no dedicated tool exists,' giving a clear routing condition. It stops short of naming alternatives or warning against using it when a dedicated destructive operation tool exists.

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