generate_postmortem

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

The description explicitly states 'Behavior: read-only', details output format ('markdown' vs 'json'), and documents output caps (timeline 20 rows, etc.). With no annotations, it fully carries the burden of behavioral disclosure.

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-structured: opening sentence defines purpose, then usage guidance, prerequisites, behavior, output details, and related tools. Every sentence adds information 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 lack of output schema and annotations, the description provides complete context: purpose, prerequisites, behavior, output format and limitations, and links to sibling tools. No gaps remain.

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 coverage is 100%, and the description adds value by explaining defaults ('duration' default '1h') and behavioral differences between 'markdown' and 'json' formats regarding data completeness and capping.

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's action ('stitch... into a single... report'), the resource ('post-mortem report'), and the scope ('one service over a given window'). It distinguishes itself from sibling tools by aggregating multiple primitives.

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?

Explicitly provides when to use ('after an incident, when... on-call can read in 60 seconds') and when not to use ('instead of poking the individual tools'). Also lists prerequisites for different data sources, guiding appropriate usage.

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