inbox_save_curation

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

No annotations provided, but description discloses key behavior: stamps Gmail historyId to keep verdict valid until thread changes, and makes inbox_get_curation near-free. No contradictions.

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?

Approximately 80 words, well-structured, front-loaded with purpose, no redundant sentences. Each sentence earns its place.

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 presence of an output schema (not shown), description covers input parameters adequately and explains postcondition. Missing nothing critical for a save operation.

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?

Description lists the fields of ThreadJudgment (bucket, importance, summary, suggested action, reasoning/confidence) but does not mention user_id or curator_version. Schema coverage is 0% for properties, so description adds some value but not fully comprehensive.

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?

Clearly states the action ('bank triage judgments into curation ledger') and the resource, distinguishes from siblings like inbox_get_curation and inbox_search by indicating sequence.

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?

Explicitly says 'Call this after reading and reasoning over threads (typically from inbox_search)', providing clear when-to-use context, though no explicit when-not or alternatives.

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