delete_release_from_user_collection_folder

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

No annotations provided, so description must disclose behavioral traits. Only states 'Remove' (destructive) and a numeric constraint, but lacks details on reversibility, authentication needs, error states, or side effects.

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 concise (two sentences) but at the cost of omitting necessary information. It front-loads the action but lacks parameter details, making it minimally adequate.

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 4 required parameters, no output schema, and no annotations, the description is incomplete. It doesn't explain success/failure responses, the relationship between release_id and instance_id, or prerequisites like folder existence.

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?

With 0% schema description coverage, the description should explain parameters. It only mentions 'folder_id must be non-zero', leaving username, release_id, and instance_id unexplained. The ambiguous 'instance_id' requires clarification.

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?

The description clearly states the action ('Remove an instance of a release from a user's collection folder') and uses specific verb and resource. It distinguishes from siblings like 'add_release_to_user_collection_folder' and 'move_release_in_user_collection', though not explicitly.

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?

No guidance on when to use this tool versus alternatives like 'move_release_in_user_collection' or 'delete_user_collection_folder'. Only constraint 'folder_id must be non-zero' is given, but no context on prerequisites or exclusions.

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