Remove User from Collection (POST)

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

Annotations already indicate destructiveHint=true (removal) and idempotentHint=true (safe to retry). The description adds no further behavioral context, such as whether the operation is reversible, what happens to associated data, or permission requirements. The phrase 'using the POST endpoint' is implementation detail, not behavioral transparency.

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 a single sentence with no wasted words. It is front-loaded with the core purpose. However, it could be slightly more informative without being verbose.

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 simple operation (2 required params, no output schema, annotations present), the description is minimally complete. It doesn't explain return value, side effects, or error conditions. For a destructive but idempotent operation, more context on what happens when the user is not in the collection would be helpful.

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 both parameters described ('Collection ID', 'User ID to remove'). The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema handles parameter documentation.

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 name 'transkribus_coll_remove_user' and title 'Remove User from Collection (POST)' clearly indicate the action (remove) and resource (user from collection). The description restates this with the same specificity. It distinguishes from siblings like 'transkribus_coll_user_add' or 'transkribus_coll_user_update_role' by focusing on removal.

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 no guidance on when to use this tool vs alternatives. For example, it doesn't mention that 'transkribus_coll_user_add_or_modify' could add or modify, or that 'transkribus_coll_user_update_role' changes roles. No mention of prerequisites or conditions.

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