add_note

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Create', implying a mutation, but does not explain requirements (e.g., file format, permissions), side effects (e.g., overwriting existing notes), or the role of output_file. The minimal verb 'Create' gives a hint but almost no operational detail.

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 description is a single sentence, which is concise, but it is under-specified rather than appropriately sized. Given the tool has three parameters and an output schema, a one-liner that omits parameter semantics and usage context does not earn its place; it inadequately addresses the tool's complexity.

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 is severely incomplete for a tool with 3 parameters, no annotations, and an output schema. It does not explain the JSON payload format, what deck_name does, how output_file is used, or any edge cases. An agent cannot confidently call this tool correctly without further investigation, making it inadequate in context.

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 0%, so the description must compensate by explaining the three parameters (deck_name, input_file, output_file). It does not mention any of them. The description adds no value beyond the bare property names in the schema, failing to clarify that input_file is the JSON payload path, deck_name is optional, and output_file likely stores results.

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 states a clear action ('Create') and resource ('new flashcard note') with a specific source ('JSON file payload'), making it easy to understand the basic purpose. However, it does not differentiate from sibling tools like add_cloze_note or add_notes_batch, which also create notes, so it falls short of a 5.

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 guidance on when to use this tool versus alternatives. It does not mention that add_cloze_note is for cloze deletions, add_notes_batch handles multiple notes, or any other selection criteria. An agent would have to infer usage from the name alone, providing no help in choosing among siblings.

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