apply_report_template

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

With no annotations, the description carries the transparency burden. It discloses that the tool applies theme, wallpaper, canvas-preset, and nav settings, and explains that the page parameter targets wallpaper and canvas (defaulting to the first page). It does not mention whether existing settings are overwritten or how errors are handled, but the core behavior is clearly described.

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 two sentences, immediately front-loaded with the primary purpose. Every phrase earns its place, providing the template structure and page behavior without redundancy.

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 moderate complexity and absence of an output schema, the description is complete: it defines the bundle, explains the template JSON, specifies page behavior, and notes the round-trip with save_report_template. No important context seems missing.

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 schema only provides brief descriptions for template and page, but the tool description elaborates the template structure thoroughly (theme, wallpaper, canvas, nav with optional fields) and clarifies page affects only wallpaper and canvas. This adds significant meaning beyond the schema and compensates for the gaps.

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 clearly states the tool applies a reusable REPORT TEMPLATE, a bundle of theme, wallpaper, canvas-preset, and nav settings. It distinguishes itself from sibling tools like apply_report_theme (theme only) and save_report_template (saving) by emphasizing the one-call bundle and round-trip behavior.

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 in the context of applying a complete pre-defined template rather than individual settings, and mentions round-tripping with save_report_template. However, it does not explicitly state when to avoid the tool or compare to setting individual properties, so it falls short of a 5.

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