generate_fleet_summary

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

Description only adds 'Free' beyond annotations. Annotations show destructiveHint=false but no other behavioral context. No mention of auth requirements, rate limits, data persistence, or output behavior. For a tool with no readOnlyHint, it should clarify if it generates state changes.

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?

Description is very short (one sentence plus 'Free'). While concise, it is under-specified for a tool with 6 parameters. The key information about free status is present but could be integrated more naturally.

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?

Despite having no output schema and 6 parameters, the description is minimal. It does not explain the output format, how parameters like ritual_strip or response_profile affect results, or how this tool differs from other summary generators. The tool appears moderately complex but description lacks completeness.

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?

Schema description coverage is 100%, so the schema fully documents parameters. The description does not need to add param info, but also misses any contextual semantics like typical usage of focus or response_mode. Baseline score 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?

Description clearly states the tool generates a fleet summary with specific content types (patterns, health, alerts, actions), and mentions it is free. However, it does not explicitly distinguish from sibling tools like generate_controller_brief or generate_incident_rca, which have overlapping summaries.

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 guidance on when to use this tool versus alternatives. The only extra hint is 'Free', which is not a usage guideline. Among many sibling tools, there is no context for appropriate use cases.

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