organization_write

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful constraint that deletion is out of scope and that permissions arrive as a JSON object, but says nothing about required permissions, validation failures, or what an update overwrites. With annotations carrying the safety burden, this is adequate but not rich.

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?

Four short sentences, front-loaded with the create/update scope and with no filler. Slightly fragmented, but every sentence contributes a distinct fact.

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?

An output schema exists so return values need no explanation, and annotations cover the mutation profile. However, for a 9-parameter write tool with 0% schema coverage, the description leaves too much parameter meaning (action_name, organization_type values, update overwrite behavior) to inference.

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 0% across 9 parameters, so the description must carry the full burden. It only hints at relationship fields generally and clarifies permissions_json, while the required action_name and organization_type (with no enum listed) and the distinction between item_id, company_id, and manager_id remain unexplained.

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 verb pair (create or update) and the exact resources it targets (Snipe-IT company, department, or group), and explicitly excludes delete. An agent can tell this apart from organization_search (read) and delete_resource (removal) without opening any schema.

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?

"Use only for requested writes" gives a clear when-to-use condition, and "cannot delete" establishes a when-not boundary that routes deletion elsewhere. It stops short of naming the alternative tool, so it is strong but not fully explicit.

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