compare_site_performance

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

No annotations are provided, so the description must fully convey behavioral traits. It implies read-only analysis but does not explicitly state safety, idempotency, or side effects. The mention of 'analyzes' suggests no mutations, but it is not explicit.

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 reasonably concise with the core purpose front-loaded, but the inclusion of a conflicting args section and a 'Returns' line that likely duplicates output schema info reduces efficiency. Every sentence should be earned.

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?

Even with an output schema, the tool fails to provide context on when to compare performance vs. get individual metrics. The misleading args section and lack of usage guidance leave the agent underinformed for correct invocation.

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 declares zero parameters, but the description lists 'Args: settings: Application settings'. This directly contradicts the schema, confusing agents. Schema coverage is 100% but the description adds misleading information.

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 compares performance metrics across all sites, listing specific metrics like uptime, latency, bandwidth, and health status. However, it does not explicitly distinguish itself from similar sibling tools such as 'get_cross_site_statistics' or 'get_internet_health'.

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, nor are there any prerequisites or exclusions mentioned. The description is purely declarative.

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