http_diff

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

With no annotations, the description fully covers behavioral traits: stateless operation, input format options (strings or dicts), and detailed report content including status transitions, header diffs, cookie attribute diffs, and body diff. It is transparent about what the tool does.

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 with line breaks and bullet points. It front-loads the main purpose and uses clear, efficient language. Every sentence adds value.

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 there is no output schema, the description fully explains the report contents (status transitions, header diffs, cookie diff, body diff). Input formats are well-specified. The tool is simple (stateless, two inputs) and the description covers all needed context.

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 provides only generic titles for parameters. The description adds crucial meaning: 'Inputs may be raw HTTP response strings (status line + headers + body) or dicts shaped...' This clarifies the expected structure beyond the 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 diffs two HTTP responses with security-relevant findings. It specifies the resource (HTTP responses) and the action (diff). No sibling tool duplicates this function, so it distinguishes effectively.

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 description implies when to use (comparing HTTP responses for security analysis) and notes statelessness. It doesn't explicitly state alternatives or when not to use, but the unique functionality makes the context clear.

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