saved_delete

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

No annotations provided. Description indicates 'Remove' (mutation) and 'undocumented session endpoint' (potentially unstable), but does not disclose side effects, idempotency, or authentication requirements beyond implying a session.

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?

Very concise single sentence that front-loads the purpose. However, it could be slightly more structured while remaining brief.

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 that an output schema exists, the description minimally covers the objective. However, for a deletion tool, more context (e.g., confirmation, permanence) would improve completeness.

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 100%, so baseline is 3. The description adds no additional meaning beyond the schema's field descriptions, which are already clear (e.g., timestamp, container ID, type).

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 'Remove a saved-for-later item' clearly states the verb and resource, and the parenthetical '(undocumented session endpoint)' adds useful nuance. It distinguishes from siblings like 'saved_add' and 'saved_list'.

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 (e.g., saved_list or saved_delete). The description only mentions it's undocumented, which is not actionable for usage decisions.

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