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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral context beyond annotations: it discloses the categories of returned data, which widgets are renderable versus not, why charts and heatmaps are excluded, and that it mirrors a specific API endpoint. It does not mention pagination or response shape details.

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 definition is front-loaded and two sentences with no wasted text. The parenthetical examples and caveats are dense but each clause contributes to understanding what the tool returns or how to use its output.

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?

With no output schema and no parameters, the description carries the burden of explaining the return contents. It does so adequately by describing presets, renderable widgets, supported cost-scope types, excluded widgets, reasons, and the `catalog_id` usage needed for downstream report creation.

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?

This tool has zero input parameters, so the baseline is 4. The description mentions downstream use of `catalog_id`s, but there are no parameters whose semantics need additional explanation.

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 and resource: listing what a scheduled report's layout can be made of. It enumerates presets, renderable dashboard widgets with supported cost-scope types, and non-renderable widgets with reasons, which distinguishes it from generic dashboard widget catalog tools.

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?

It gives clear usage context by saying the returned `catalog_id`s are used with create_scheduled_report / update_scheduled_report's `layout`. However, it does not explicitly name alternatives or when-not-to-use guidance, such as when list_dashboard_widget_catalog would be more appropriate.

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