saved_add

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It only states a write operation ('Save') without detailing side effects, required permissions, rate limits, or whether the operation is reversible. The mention of being 'undocumented' is vague and not a behavioral disclosure.

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 extremely short (one sentence), but conciseness should not come at the expense of essential information. It omits param semantics and behavioral details, making it under-informative rather than appropriately concise.

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 tool has 4 parameters with no schema descriptions and no annotations, the description is critically incomplete. It fails to explain the purpose of each parameter, the expected behavior, or the return value (despite an output schema existing). The agent lacks sufficient context to use the tool reliably.

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%, and the tool description provides no explanation of the parameters (item_type, item_id, ts, date_due). The agent has no information about their meanings, formats, or constraints beyond the schema types and required status, which is insufficient for correct invocation.

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 clearly states the action ('Save a message for later') and implies the resource is a message. The verb 'Save' and the context of 'for later' convey a storage/retrieval function. However, it does not distinguish from similar sibling tools like stars_add or pins_add, leaving ambiguity about the specific type of 'saved' item.

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 vs. alternatives like saved_delete or other save actions (stars_add, bookmarks_add). The parenthetical 'undocumented session endpoint' hints at instability but provides no practical usage direction or prerequisites.

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