manage_models

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

Annotations already declare destructiveHint=true, so agents know this tool can be destructive. The description adds that delete is an operation and lists required IDs, but does not go beyond that to explain side effects (e.g., whether associated assets are affected) or authentication needs. It does not contradict annotations, but adds limited behavioral context.

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 well-organized with a clear lead sentence, a bulleted list of operations, and a return-value note. It is succinct, front-loaded with the tool's purpose, and every line contributes operational value with no redundancy.

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 tool's complexity (8 parameters, 6 actions, output schema present), the description covers all actions and required parameters, plus it mentions the return format. It does not detail pagination/filtering behaviors for list/assets, but those are already covered by the schema, so the description is comprehensive for an agent.

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?

While the schema has 100% parameter description coverage, the description adds operational nuance beyond the schema—notably that 'create' requires model_data with name and category_id, and that model_id is needed for get/update/delete/assets. This helps the agent avoid invalid calls and is value-add over the schema.

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 explicitly states 'Manage Snipe-IT asset models with CRUD operations' and enumerates all six supported actions with required parameters, clearly distinguishing this tool from sibling tools like manage_assets and manage_categories. The resource scope is unambiguous and operationally detailed.

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 provides clear context for when to use the tool (any CRUD operation on asset models) but does not explicitly name alternative tools or exclusion criteria. The resource definition implies when it is the right choice, so this is a solid 4 rather than 5.

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