save_reading_item

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds that idempotency is keyed by 'source_url' and 'content_hash', and mentions 'schema-stable' and 'configured local storage backend', which enriches behavioral understanding beyond annotations.

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?

Two sentences, no redundant words. First sentence states purpose, second adds a key behavioral trait. Efficient and clear.

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?

Despite having an output schema and nested objects, the description does not explain return values, error conditions, or validation behavior. For a tool that takes a complex object, this lacks essential contextual detail.

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%, so the description must fully compensate. It only mentions 'schema-stable ReadingItem', but does not explain the 'item' object structure, required fields, or the meaning of the 'store' parameter. This is a significant gap.

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 verb 'save' and the resource 'ReadingItem' into a 'local storage backend'. It also specifies idempotency, distinguishing it from reading/sibling tools like 'read_url' or 'library_get'.

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 implies usage when saving a ReadingItem, but does not explicitly compare to sibling tools (e.g., library_list, library_search) or provide when-not-to-use guidance. The idempotency detail hints at safe reuse, but lacks clear contextual directive.

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