export_to_html_report

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

With no annotations provided, the description must disclose behavioral traits, but it only mentions 'standalone' and 'optional visual charts' — features rather than behaviors. It does not describe return format, side effects, prerequisites, or limitations, which is a significant gap.

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 short, front-loaded sentences with no fluff. Every word contributes to the core message, making it very concise and scannable.

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?

The tool has a dual-mode results parameter and no output schema, yet the description does not explain what the tool returns (HTML string, file path, etc.) or mention the dual-mode behavior. The schema covers parameters, but the description omits essential context for confident use, making it incomplete.

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 input schema covers all three parameters with descriptions, including the dual nature of the results parameter (object or URL). The description adds no extra semantics beyond what the schema already provides, so the baseline of 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 description clearly identifies the primary action: generating a standalone HTML report with styling. This distinguishes it from CSV/Excel/JSON export tools, but it does not explicitly differentiate from other report-generating siblings like generate_summary_report or generate_dashboard.

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?

There is no guidance on when to use this tool versus other export/reporting tools. The description does not mention alternatives, exclusions, or typical use cases, leaving the agent without decision-support.

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