List Edge Stats report presets

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

With no annotations, the description carries the burden, and it does disclose the catalog is precomputed nightly, explains what each preset provides, and states that the return value is preset ids for edge_report. It does not discuss auth, rate limits, or exact output shape, but for a simple read/list tool these omissions are minor.

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 compact: it front-loads the catalog concept, gives concrete examples, explains the presets' value, and closes with the output relation to edge_report. Every sentence earns its place and there is no fluff.

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?

For a simple optional-parameter list tool with no output schema and no annotations, the description covers what the tool does, what its data represents, and how the returned ids are used. The category behavior is already documented in the schema, so nothing critical is missing for an agent to call it correctly.

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 only parameter, category, has a schema description ('Narrow to one category (the result lists all categories)'), giving 100% schema coverage. The tool description itself does not mention the parameter, so it adds no additional meaning beyond the schema; baseline 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 title and description clearly state the tool lists Edge Stats report presets and returns preset ids for edge_report. This distinguishes it from the edge_report tool, which likely consumes those ids rather than listing 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 description establishes the tool as a catalog of precomputed session-statistics questions and explicitly ties the output to edge_report, making it clear this is the discovery/preview step before running a report. It does not explicitly contrast with siblings or say when not to use it, but the context is clear.

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