list-report-presets

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

No annotations are provided, so the description must carry the behavioral burden. 'List' implies a read-only operation, and 'built-in' suggests stable presets, but the description does not disclose return format, ordering, or pagination behavior. For a simple zero-parameter listing tool this is adequate but not rich.

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 entire description is a single focused sentence with no filler. It front-loads the action and resource and includes the key relationship to run-adhoc-report without unnecessary detail.

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 tool has no parameters and no output schema, the description is nearly complete: it tells an agent what the tool returns (built-in field-set preset names) and why that matters (they can be executed by run-adhoc-report). It could optionally specify whether return values include only names or richer preset metadata, but this is a minor gap.

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?

The tool has zero parameters, and the empty schema already fully documents this. The description adds that presets are identified/executed by name, which is useful context for how results may feed into run-adhoc-report, though no parameter-level documentation is needed.

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') plus a clear resource ('built-in field-set presets') and explicitly ties them to run-adhoc-report by name. This differentiates it from siblings like list-custom-reports, which lists custom reports rather than built-in presets.

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 phrase 'that run-adhoc-report can execute by name' gives clear context: this tool is the discovery mechanism for preset names to pass to run-adhoc-report. It does not explicitly list excluded alternatives, but the built-in/custom distinction and named target are enough to guide selection.

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