Remove Doc From Collection

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that removing is non-destructive and doesn't alter rules, which is useful context beyond the annotations. It doesn't describe error behavior for non-members, but that's a minor gap given the simple scope.

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 two sentences long, with no filler. It immediately states the action and its non-effects, making it concise and well-structured.

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 a single-document removal with annotations, full schema coverage, and an output schema, the description covers the operation and its boundaries. It lacks explicit mention of return values or error cases, but the output schema likely covers that. Overall, it is complete for the tool's complexity.

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?

All three parameters have descriptions in the schema, covering 100% of them. The description does not add additional meaning beyond what the schema provides, so a baseline of 3 is appropriate.

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 'Remove a document id from an AFFiNE collection allow-list' – a specific verb+resource+object. It explicitly distinguishes itself from deleting the document or changing collection rules, differentiating it from siblings like delete_doc, update_collection_rules, and add_doc_to_collection.

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 explains the operation's scope and exclusions ('does not delete the document or change collection rules'), which signals when to use this instead of destructive or rule-modifying tools. However, it doesn't explicitly name alternatives like add_doc_to_collection, so some inference is needed for the when-to-use guidance.

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