list_dummy_notes

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

Annotations already cover readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is disclosed. The description adds valuable context that the returned note_id is meant to be passed to other tools and that the list contains notes with difficulty levels, line counts, etc. This goes beyond the annotations without contradicting them.

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 well-structured: a one-sentence purpose, a usage note about the workflow, a Returns section, and clear examples. Every sentence adds value, and the content is front-loaded with the main purpose.

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?

For a no-parameter list tool with a rich output schema and safety annotations, the description provides purpose, usage guidance, return format hints, and examples. It covers everything an agent needs to know to invoke it correctly and understand its role in the workflow.

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?

There are zero parameters, so schema coverage is complete and the description need not explain parameter semantics. The baseline of 4 applies. The description does mention the return structure, which is helpful but not about parameters.

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 clearly states it lists synthetic meeting notes from an education package, and distinguishes itself from read_meeting_note by noting that you should use that tool when you already have a note_id and need the original text. The verb 'list' and resource are explicit.

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?

It explicitly says this is the starting point for meeting minutes work and provides a concrete example of when NOT to use it (when you already have note_id and need the original text), naming the alternative tool read_meeting_note. This gives agents clear selection criteria.

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