koios_ogmios

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

No annotations are present, so the description carries the full burden for behavioral context. It only states the basic action and provides no details on authentication, rate limits, error formats, response structure, or whether operations are read-only. This is a significant gap for a generic proxy tool.

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, front-loaded sentence that efficiently conveys the purpose, resource, and example methods. It contains no wasted words and is easy to parse.

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?

As a generic proxy to Ogmios, the description provides the core concept but lacks an enumeration of supported methods beyond the 'etc.', expected response behavior, or any restrictions. The absence of an output schema increases the need for such context, making the description minimally complete.

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 100% as both parameters have descriptions. The tool description adds some examples for the 'method' parameter but does not go beyond the schema's 'Ogmios JSON-RPC method name' and 'Optional parameters' text. The baseline of 3 is appropriate since the schema carries the parameter semantics.

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 action 'Send a JSON-RPC request' and the resource 'Ogmios endpoint via Koios'. It also gives specific method examples (queryLedgerState, queryNetwork) which distinguishes it from sibling tools that are all dedicated Koios API endpoints.

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?

Usage is implied: since this is the only tool mentioning Ogmios, an agent can infer it is for Ogmios methods not covered by other Koios endpoints. However, no explicit when-to-use vs alternatives or exclusion criteria are provided.

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