pgiq_best

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

No annotations provided. The description mentions re-weighing pillars and returning rationale, but does not disclose whether the tool is read-only, requires authentication, or has any side effects. More behavioral context would be helpful.

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, under 50 words, front-loaded with main purpose, efficient and no superfluous text.

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?

Tool has 4 parameters and no output schema. Description explains the purpose and lens mechanism but omits details on output format, pagination behavior (limit), tier definitions (min_tier), and error handling. Could be more thorough.

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% (baseline 3). The description adds meaningful context for the 'lens' parameter by explaining the re-weighing of pillars. Other parameters (group, limit, min_tier) are not elaborated beyond schema, so minor added value.

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 the tool 'Get a ranked best-market decision for siting or scheduling a large electricity load', specifies the resource (markets), and distinguishes it as the 'decision endpoint' from siblings.

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 this is the final decision tool but does not explicitly state when to use it versus alternatives like pgiq_rating or pgiq_cheapest_window. No prerequisites or exclusions are mentioned.

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