list_demandnote_requests

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states the action ('List') but does not mention whether this is a read-only operation, any authentication requirements, or potential side effects. It also doesn't clarify pagination behavior or that results are sorted/ordered in any way.

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 a single concise sentence with a helpful parenthetical. It is front-loaded with the verb and resource, contains no redundant information, and every word earns its place. This is an model of brevity.

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?

The tool is a simple list operation with well-documented parameters, but there is no output schema and the description doesn't mention what the response contains (e.g., fields, pagination metadata). Given the simplicity, the lack of return-type detail is a minor gap, but the description is not fully self-contained for an agent.

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 coverage is 100%, with each parameter (page, items, status) having a description. The tool description itself adds no parameter semantics, but the schema already provides sufficient meaning, so the baseline of 3 is 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?

The description uses a specific verb 'List' and a specific resource 'demand note requests', with a clarifying parenthetical 'payment demands from management' that distinguishes it from other list tools in the sibling set. This makes the tool's purpose unambiguous.

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 gives no guidance on when to use this tool versus alternatives. It doesn't mention any filtering or search alternatives, nor does it provide context about when this list is appropriate. The parenthetical gives a hint about the domain but is not explicit usage guidance.

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