List Request notes

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about pagination, sorting, search criteria, permissions, or return shape. For a tool with a nested list_info control object, this is a severe 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 single sentence is short, but this is under-specification rather than conciseness. It wastes no words yet conveys almost no information, so brevity here does not earn credit.

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?

Given a nested object parameter, pagination controls, search criteria, and no annotations or output schema, the description is wholly inadequate. An agent cannot determine how to page, filter, or interpret results from this text.

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 adds no parameter meaning whatsoever. The nested list_info object (row_count, sort_field, start_index, search_criteria, etc.) and the required request_id are completely undocumented beyond their machine-readable types.

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 restates the tool name and title almost verbatim ('List request notes'), giving only a bare verb+resource with no scope, filtering behavior, or distinction from sibling list tools such as list_request_tasks. It is effectively a tautology rather than an informative statement of purpose.

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 this tool versus alternatives like get_request_note, get_request, or list_request_tasks, and no prerequisites or context are mentioned. The agent is left to infer usage entirely from the name.

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