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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and openWorldHint=false, covering the safety profile. The description adds the pagination nature and the set of statuses returned, which is genuinely useful, but pagination is already evident from the limit/cursor schema fields and the closing phrase 'No server interpretation starts' is opaque rather than informative.

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 first sentence is dense and front-loads the important scoping and filter information well. The second sentence, 'No server interpretation starts,' is cryptic and does not clearly earn its place, weakening an otherwise efficient structure.

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?

An output schema exists, so return values need not be explained, and annotations plus 100% schema coverage handle most structured detail. The description covers what is listed, the statuses, and the optional filter, leaving only usage routing and the meaning of the trailing phrase as gaps.

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 all four parameters are already documented, including the projectId and attachmentId provenance. The description restates the project scoping and attachment filter but adds no format, syntax, or edge-case meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Returns a paginated list of ... reference notes') and scopes it by status (approved/proposed/rejected) and optional attachment filter. It implicitly distinguishes itself from the write siblings studio_reference_note_add and studio_reference_note_update, though it never names an alternative explicitly.

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 only implied: an agent can infer it reads existing notes rather than creating them. There is no explicit when-to-use, when-not-to-use, or routing to studio_references_list / studio_reference_note_add, so the guidance gap is real but the read/list intent is clear from context.

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