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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds that results are cursor-paginated and can be hydrated to a relation depth, which is genuine behavioral context, but it omits the 60-item cap behavior and what pageInfo/return shape the caller receives.

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?

Three short sentences, front-loaded with the core action and then the notable capabilities and endpoint. No filler, though the REST endpoint reference is mildly redundant with the tool name.

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 read-only list tool with a fully documented schema and no output schema, the description covers scope, pagination, filtering, and ordering adequately. The only real gap is that result-shape and default-paging behavior are left to the schema annotations.

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%, so every parameter (depth, limit, filter, order_by, both cursors) is already documented with syntax examples. The description's mention of "raw filter/order_by" and "relation depth" merely mirrors the schema and adds no new semantics, making the baseline 3 appropriate.

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 ("List/filter notes") and discloses the underlying REST operation, which cleanly separates it from twenty_get_note and the create/update siblings. It is clear without explicitly naming an alternative tool.

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 only asserts capability (pagination, raw filter/order_by, depth) and never says when to reach for this list tool versus twenty_get_note or how to narrow results. No prerequisites or exclusions are given, leaving usage entirely to inference from the name.

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