check_thresholds

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

With no annotations provided, the description must disclose behavioral traits, but it only states that thresholds are checked against current values. It does not mention side effects, read-only nature, permissions, error conditions, or return format, leaving significant behavioral ambiguity.

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 a single concise sentence with no fluff, but it is under-specified for a tool with 5 parameters and no schema descriptions. It is not as vacuous as 'Process', but it does not provide enough detail to be useful.

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 tool's complexity (5 parameters, no output schema, no annotations), the description is completely inadequate. It fails to explain the structure of threshold rules, the meaning of format, the role of RPC URL and contract address, or the expected return value, making correct invocation impossible.

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 description coverage is 0%, and the description does not compensate. No parameter is explained—neither 'rules' (the threshold list) nor 'format', 'chain', 'rpcUrl', or 'contractAddress'. The tool description adds no semantic meaning beyond what the bare schema shows.

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 "Check metric thresholds against current values" clearly identifies the action (checking thresholds) and the resource (metric thresholds), and it distinguishes itself from sibling tools such as quote_metrics or check_staleness. However, it could be more specific about the input rules structure and the nature of the output.

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 provides no guidance on when to use this tool versus alternatives like quote_metrics or get_health. It does not mention any context, prerequisites, or situations where this tool is preferred.

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