opencrater_supported_tools

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

No annotations provided, so description carries full burden. Description is a single noun phrase with no behavioral details: no mention of read-only nature, side effects, or output characteristics. Fails to disclose basic operational traits.

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?

Description is extremely short (one noun phrase), which is concise but under-specified. Lacks complete structure (no verb, no object). Every sentence should earn its place; this one does not.

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 no parameters and no output schema, the description should at least explain the return value or purpose more completely. It only says 'the AI coding tools' without specifying that this tool returns a list or provides information.

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 has 0 parameters with 100% trivial coverage. Baseline is 4, but description adds no meaningful context beyond the schema; does not describe what the tool returns or how to interpret results.

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 is a noun phrase lacking a verb: 'The AI coding tools where OpenCrater Blips can render.' It does not clearly state what action the tool performs (e.g., list, get, retrieve). Vague purpose, not distinguishing 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?

No guidance on when to use this tool versus alternatives (siblings opencrater_get_started and opencrater_network_stats). No context about prerequisites or typical scenarios.

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