crypto_txs

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

No annotations are present and the description is just the tool name. The description discloses nothing about side effects, safety, rate limits, or any behavioral traits, placing the full burden on the description which it fails entirely.

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?

While the description is extremely short (one word), this is under-specification rather than conciseness. It lacks any structuring or content that would help an agent understand the tool, similar to the 'Process' example in the calibration.

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?

For a tool named 'crypto_txs' with no description, no annotations, no output schema, and no parameters, the information is entirely inadequate. An agent has no clue what transactions are involved, what inputs/outputs to expect, or how to invoke it correctly.

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 schema has zero parameters, and the schema coverage is 100% (vacuously). With no parameters to describe, the baseline of 4 applies; the description need not explain parameters, though it also adds no additional parameter-related meaning.

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?

Tautological: description restates name/title.

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?

There is no guidance on when to use this tool versus alternatives. No context, prerequisites, or exclusions are provided, leaving the agent to guess its purpose.

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