write_demo_note

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

No annotations are present, so the description carries the burden. It discloses 'append-only', which is a key behavioral trait (notes cannot be overwritten/deleted), but does not mention permissions, return values, or error conditions. This is adequate for a simple write tool but leaves gaps.

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?

Single sentence with every word informative; front-loaded action 'Store a note' and qualifier 'append-only' conveys key behavior efficiently.

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 tool is simple (one param) and the description covers its core nature (append-only write to a synthetic sink). No output schema exists, but for a write action, the lack of return value description is acceptable. It could benefit from clarifying when to use vs siblings or any side effects, but overall sufficient.

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% with 'Synthetic note text.' for the note parameter. The description's 'Store a note' adds no additional meaning beyond the schema. Baseline 3 applies since schema fully covers parameter.

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 uses the specific verb 'Store' and identifies the resource as 'note in the append-only synthetic research sink', clearly distinguishing it from sibling tools like read_demo_record and send_demo_message. The 'append-only' qualifier further clarifies the operation's nature.

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?

There is no explicit comparison to sibling tools or exclusions, but the description implies this tool is for writing notes rather than reading records or sending messages. The 'synthetic research sink' context gives some situational clue, but no when-to-use guidance is given.

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