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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no note about ordering, pagination, or how many notes are returned for a heavily used label.

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?

A single front-loaded sentence with zero filler that states the resource and its filter immediately. Nothing in it needs trimming.

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 an output schema present, an annotated single-parameter read tool needs little prose, and this definition covers the essentials. A brief note on result ordering or volume for a broad label would make it complete rather than merely adequate.

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% and the single parameter is documented in-schema, including a cross-reference to the localLabelId field of get_user_labels. The description's 'label/tag' phrasing is consistent but adds no format or ID-resolution detail beyond the schema.

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?

States a specific verb and resource ('Get all notes') plus the filtering dimension ('specific label/tag assigned'), so an agent knows exactly what it returns. It does not explicitly differentiate itself from lookalike siblings such as get_recent_notes or search_notes, which also return note collections.

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?

The description conveys the retrieval filter but gives no when-to-use guidance, no conditions selecting it over get_recent_notes/get_note_labels/search_notes, and no prerequisites. The use case is only weakly implied by the presence of a label filter.

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