compare_requests

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

The description does not disclose any behavioral traits. It is unclear if the tool is read-only, whether it requires special permissions, or what happens if one of the IDs is invalid. With no annotations provided, the description carries the full burden, and it fails to provide any behavioral context.

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 very short, which is concise, but it lacks structure. It does not include any headings or bullet points, and the single sentence is somewhat vague. For a simple tool this may be sufficient, but it does not fully earn its place as it omits important details.

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 an output schema and the complexity of comparing two requests, the description is incomplete. It does not explain what the comparison yields (e.g., a diff, side-by-side metrics, etc.), nor does it mention any prerequisites or limitations. The agent has insufficient context to use this tool effectively.

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 already describes the two parameters with clear names and descriptions ('First request ID', 'Second request ID'). The description adds no additional meaning beyond what the schema provides. Since schema coverage is 100%, baseline 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?

The description 'Compare two requests side by side' clearly states the action (compare) and the objects (requests). However, it lacks specificity on what aspects are compared (e.g., timeline, performance, or raw data), and does not differentiate from sibling tools like get_request or list_requests which could be used in combination.

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 is provided on when to use this tool versus alternatives. For example, it could be used to compare performance or request details, but without such context, the agent may not know if this is the appropriate tool compared to analyzing individual requests separately.

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