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

The description contradicts the provided annotations. It says append=true adds to an existing note, making repeated identical calls non-idempotent despite idempotentHint=true, and says clearing text deletes the note despite destructiveHint=false. Per the rubric, any contradiction scores 1.

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 main operation is front-loaded and the parameter explanations are short. A little redundancy with the schema exists (e.g., restating emoji and append), but every sentence communicates something relevant.

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?

The description covers create/replace/append/delete modes and return behavior, but it does not clarify behavior when optional text is omitted (only date is required) or the default for append. Combined with the annotation contradictions, an agent cannot reliably predict the tool's side effects.

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 coverage is 100%, so the schema already documents date, text, emoji, and append. The description adds value by spelling out that clearing text deletes the note and emoji is optional, but it leaves ambiguity about whether omitting text is the same as clearing it and what the default for append is.

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?

States a specific action and resource: create or replace a daily note for the authenticated user. It clearly distinguishes itself from sibling tools like get_notes (read) and save_flow (flow-specific). The title and first sentence make the tool's scope unmistakable.

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 clearly indicates this is the write path for daily notes, so an agent can infer when to choose it over read siblings. It does not explicitly name alternatives or state exclusions, but the intended context is not ambiguous.

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