getIspLoad

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

No annotations provided. Description explains it retrieves traffic volume and utilization, but doesn't disclose potential rate limits, data availability, or that it targets a specific site's ISP links. Reasonable but not exhaustive.

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?

Three sentences, front-loaded with core function, no redundancy. Every sentence adds value: operation, detail, use cases.

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?

With 4 params (2 required), no output schema, description covers what the tool does and parameter roles. Lacks indication of output structure (e.g., list of links with metrics), which would help agents parse results. Still, fairly complete for a read tool.

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% with descriptions for all parameters. Description reiterates that start/end are Unix timestamps but adds no new semantic info beyond schema. Baseline 3.

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?

Description clearly states 'Get per-WAN ISP link load over a time range' with specific verb and resource. Lists use cases (load balancing, saturated links, failover) that distinguish it from sibling tools like getGatewayHealth or getTrafficDistribution.

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?

Description mentions useful scenarios but lacks explicit guidance on when not to use or alternatives. Does not state prerequisites like having a gateway with WAN links.

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