copy_day

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

Discloses key behavior (server-side, additive, covers all entry types) but omits potential failure modes, authorization requirements, or return value details. Adequate given no 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?

Concise, front-loaded with main purpose, every sentence adds value. No extraneous information.

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?

Explains overall behavior adequately for a copy tool with simple parameters. Output schema exists so return values not needed. Minor gaps like edge case behavior (e.g., same date) not covered.

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?

Adds meaning beyond schema by specifying format YYYY-MM-DD for both parameters. Schema covers 0%, so description compensates well.

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 verb (copy), resource (all diary entries), and scope (from one date to another). Distinguishes from sibling tools that operate on individual entries.

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?

Explains that it is server-side, copies all entries additively, implying use when duplicating date data without overwriting. Does not explicitly mention alternatives but context makes it clear.

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