get_health

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool is free and requires no credentials, and enumerates the specific behavioral output (liveness, payment mode, OFAC status, signals freshness). It doesn't explicitly state it's read-only, but the 'Check' verb implies non-mutating behavior.

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 exceptionally concise: two sentences that front-load the purpose, then specify the exact sub-checks and access requirements. Every clause adds useful information, with no filler or redundancy.

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 there is no output schema, the description does a good job of informing the agent what the response will contain by listing the health indicators and the signals freshness block. It could be more explicit about the overall response structure or what 'stale' means, but for a simple health-check tool, it covers the essential context adequately.

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?

The input schema has zero parameters, so the description's lack of parameter details is perfectly acceptable. Per the baseline for 0 params, a score of 4 is appropriate. The description adds value by describing the output fields, though parameter semantics are not applicable here.

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 starts with a specific verb 'Check' and resource 'Isocast API health', clearly distinguishing it from sibling data-retrieval tools. It enumerates the exact health aspects covered (liveness, payment mode, OFAC, signals freshness), leaving no ambiguity about its function.

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 clear context for when to use the tool: it's a health check and explicitly notes that it is free and requires no wallet or API key, implying it can be used without authentication. It doesn't explicitly mention alternatives or exclusions, but the distinct purpose and self-contained context make usage obvious.

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