list_notes

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

No annotations are provided and the description discloses no behavioral traits such as pagination, read-only semantics, ordering, limits, or dependency on campaignId. The agent gets nothing beyond the verb 'list'.

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 short but this is under-specification rather than efficient conciseness. It conveys no information beyond the tool name and does not earn its place as a helpful definition.

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?

With two parameters, a required campaignId, no annotations, no output schema, and many siblings, 'List notes' is far too incomplete. It omits essential context about filtering, return values, and relationship to get_note.

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%, and the description does not mention campaignId or page. The agent must guess the meaning of the required parameter from its name alone.

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 'List notes' is effectively a restatement of the tool name. It provides no detail about scope, filtering, or how this tool differs from the sibling get_note or other list_* tools.

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 list_notes instead of get_note, or when the required campaignId should be provided. An agent cannot determine whether this lists all notes or notes scoped to a campaign.

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