get_open_anomalies

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

No annotations provided, so description carries full burden. Explains that anomalies are open/unresolved, condition is active, resolution is automatic or manual. Sufficient for a read list tool, though could mention snapshot nature.

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 purpose, no extraneous text. Every sentence adds value: purpose, usage guidance, behavioral context.

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?

No output schema; description only says 'return all open anomalies'. Does not describe structure of returned data (e.g., fields like GPU ID, condition type). More detail would benefit the agent.

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?

No parameters; baseline score of 4 applies per instructions. Description adds no param info, which is acceptable when schema coverage is 100% and no params exist.

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?

Clearly states 'return all currently open GPU anomalies' with specific verb and resource. Distinguishes from siblings by mentioning 'use alongside list_alerts' and 'resolve_anomaly' for resolution.

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?

Provides explicit usage context: 'quick fleet health check alongside list_alerts'. Implicitly not for resolving anomalies (via resolve_anomaly). However, does not differentiate from sibling list_anomalies.

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