generate_summary_report

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states it generates a report and returns JSON with Markdown content, but does not disclose whether it performs read-only operations, any side effects, permissions needed, or limitations. This is insufficient for a tool that generates reports.

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 well-organized with Args and Returns sections, making it easy to scan. The formatting for date_range is slightly elaborate but serves a purpose. No fluff or redundant content is present.

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 description covers purpose, parameters, and return format, and an output schema exists so return details are not required. However, it lacks usage context and behavioral transparency, making it only minimally complete for a tool with no annotations.

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 provides zero description coverage (0%), so the description fully compensates by explaining report_type values ('daily/weekly') and date_range format with a concrete example and a warning against passing integers. This adds significant meaning beyond the bare schema.

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 generates daily/weekly hotspot summary reports, providing a clear verb ('generate') and resource ('summary report'). It distinguishes itself from sibling tools by focusing on report generation rather than analysis, though it doesn't explicitly name alternatives.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The mention of 'daily/weekly' implies scheduling context, but there is no statement of appropriate conditions or exclusions, leaving the agent to infer usage.

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