list-custom-reports

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

With no annotations, the description carries the full burden. 'List' implies a read-only operation, but the description does not disclose potential pagination, authentication needs, or the structure of the response. For a zero-parameter list tool, this is minimally adequate but not detailed beyond the core behavior.

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, direct sentence with no filler words. The key action and target resource are front-loaded, making it immediately parseable by an agent.

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 the low complexity (zero parameters, no output schema), the description gives the essential purpose. However, it does not clarify what fields the returned list contains (e.g., names, IDs) or how it differs from list-report-presets, so an agent might still lack confidence in what the tool returns. The lack of an output schema makes the description the only source of this information.

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?

There are zero parameters, so no semantic clarification is needed. The schema is fully covered by having no properties. The baseline for zero-parameter tools is 4, and the description appropriately says nothing about parameters since none exist.

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 ('List') and a clear resource ('saved custom reports available in BambooHR'). It distinguishes itself from siblings like run-custom-report and run-adhoc-report by focusing on enumeration rather than execution, making its 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 implies usage when an agent needs to see all saved custom reports, but it does not explicitly state when to prefer this over list-report-presets or run-custom-report. No alternatives or exclusions are named, leaving some inference required.

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