Generate markdown summary

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description need not restate them. But it adds essentially nothing beyond 'beautiful': no indication of where the output goes, whether anything is written, format guarantees, or error handling for malformed results.

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?

A single, front-loaded sentence with no filler. It is efficient, though 'beautiful' is subjective marketing language rather than useful specification.

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?

For a tool with two required, fully undocumented parameters, no output schema, and a non-read-only annotation, the description is far too thin. An agent cannot know what `action` should contain or what the summary renders from beyond a vague one-liner.

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 0%, so the description must compensate. 'Bulk operation results' loosely maps to the required `results` array, but the required `action` parameter is entirely unexplained, and the status/data/error/metadata shape of results is undocumented.

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?

States a specific verb (generates) and resource (markdown summary) scoped to bulk operation results, which distinguishes it from the many build/commit/git siblings. However, it does not name or differentiate against any specific alternative in a very crowded namespace.

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 phrase 'of bulk operation results' implies the usage context (call it after a bulk operation to render output), but there is no explicit when-to-use, when-not-to-use, or named alternative among the ~90 siblings. Usage is left to inference.

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