Get Available Resources

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

No annotations exist, so the description bears full responsibility. It states a read-only operation but does not disclose non-obvious behaviors such as authentication needs, rate limits, side effects, or response structure. It adds minimal context beyond the stated purpose.

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?

Two concise sentences with no fluff, front-loaded with the primary action. The description could have been expanded with relevant details without sacrificing brevity, so it is efficient though not maximally informative.

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 low complexity (2 optional params, no output schema), the description is adequate but lacks completeness. It does not explain the return format or any pagination, which would be helpful for an agent. Sibling tools provide some context but the description alone is minimal.

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%, so the baseline is 3. The description does not add meaning beyond the schema; it omits details on how 'durationMinutes' filters results or the effect of not specifying 'resourceType'. No examples or clarifications are provided.

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 retrieves total available Energy and Bandwidth across active pools, specifying a concrete verb and resource. It is distinct from siblings like 'buy_energy' (purchase) and 'get_market_overview' (broader view), showing clear differentiation.

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 usage for checking resource availability before purchase ('Shows how much resource can be purchased right now'), but it lacks explicit when-to-use or when-not-to-use guidance. No alternatives are named, though context from sibling tools suggests it's for querying.

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