reading_collect_card

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

Annotations are minimal (only title), so the description carries full burden. It does not disclose side effects, idempotency, prerequisites, or what happens to previously collected cards. Only states the action and purpose, leaving behavioral traits unspecified.

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?

Extremely concise at 10 words, but this brevity comes at the cost of completeness. The description lacks necessary details and fails to front-load critical information for tool selection. Being too short reduces usability.

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 14 parameters and no output schema or annotations, the description is severely incomplete. It does not explain the collect action's workflow, parameter usage, or return value. The tool's complexity demands far more context than provided.

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% with 14 parameters, none explained in the description. The description does not mention any parameter names, their roles, or how they relate to collecting a card. The tool's purpose is stated but disconnected from the input 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?

The description states it 'Collect[s] a small ritual reading card/bookmark' with purpose of revisiting later. The verb 'collect' and resource 'card/bookmark' are specified, but it lacks clarity on how 'collect' differs from 'save' (sibling 'reading_save_card' exists). The purpose is somewhat clear but not distinct enough.

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 'reading_save_card' or 'reading_open_card'. No mention of prerequisites or exclusion cases. The description provides no usage context beyond the basic action.

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