create_meeting_note

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

With no annotations, the description carries full burden. 'Create' implies a write operation, but there is no mention of where the note is saved, whether it's in the vault, default folder behavior, or authorization needs. Worse, it mentions 'action items' which do not appear in the schema, introducing ambiguity. This is a significant transparency gap.

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, short sentence, which is concise and front-loaded with the verb. However, it includes a stray reference to 'action items' that is unsupported by the schema, making it inaccurate. It earns a 3 because it's not overly long but sacrifices correctness for brevity.

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 create operation with no annotations and no output schema, the description is too thin. It doesn't explain return values, vault placement, or any side effects. The schema is simple, but the description still fails to paint a complete picture of what the tool does beyond the bare minimum.

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?

The schema has 100% description coverage for its five properties, so the baseline is 3. The description adds no useful parameter detail beyond the schema; instead, it introduces 'action items' which are not a property, potentially misleading the agent into thinking there is an action_items field. This actively detracts from parameter understanding.

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 the action ('create') and the resource ('structured meeting note'), and it hints at specific content (attendees, agenda) that distinguishes it from generic create_note. However, it does not explicitly differentiate from sibling tools like create_note_from_template or create_project_note, so it's clear but not fully distinguishing.

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?

Usage is implied by the tool name and description: use this for meeting notes. There is no explicit guidance on when to choose this over alternatives like create_note or when not to use it. The rubric marks implied usage as a 3.

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