reading_save_card

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

Annotations only provide title, no destructiveHint or readOnlyHint. Description implies file creation side effect but lacks details on file format, naming, overwrite behavior, or error conditions.

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?

Single sentence with no filler, but could be improved by front-loading key action and separating return value. Short but not optimally 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?

With only one parameter and no output schema, description should clarify 'collected' status, image file format, storage location, and absolute path semantics. Current description is incomplete for reliable agent invocation.

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 0%, so description must compensate. Description does not describe the 'cardId' format, valid values, or how to obtain it. No examples or constraints beyond required.

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 uses specific verb 'Render' and specifies resource 'one collected reading card' and outcome 'local image file and return its absolute path'. This clearly distinguishes it from sibling tools like reading_open_card or reading_list_cards.

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_open_card. Does not state prerequisites (e.g., card must be collected) or mention when not to use it.

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