Cross-LLM MCP Server

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 but only states the action without detailing traits. It doesn't mention whether this is read-only (likely, but not confirmed), if it requires network access, error handling (e.g., for invalid hex), or output format (since no output schema exists). This is a significant gap for a tool with potential complexity.

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, direct sentence with zero wasted words. It front-loads the core action ('Decode a Bitcoin transaction'), making it immediately scannable and efficient. Every word earns its place, adhering to best practices for conciseness.

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 complexity of Bitcoin transactions and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'decode' returns (e.g., structured data vs. raw details), error conditions, or dependencies. For a tool that could involve cryptographic parsing, more context is needed to guide the agent effectively.

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 description coverage is 100%, with the parameter 'rawHex' clearly documented as 'Transaction hex' in the schema. The description adds no additional meaning beyond this, such as format constraints (e.g., hex string length) or examples. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but doesn't detract either.

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 verb ('decode') and resource ('a Bitcoin transaction'), making the purpose immediately understandable. It distinguishes from siblings like 'get_transaction' (which likely retrieves rather than decodes) and 'decode_invoice' (which decodes a different resource). However, it doesn't specify what decoding entails (e.g., extracting inputs/outputs vs. full parsing), keeping it from a perfect score.

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. It doesn't mention prerequisites (e.g., needing raw hex data), contrast with 'get_transaction' (which might fetch from a network), or specify use cases (e.g., for analysis vs. validation). This leaves the agent to infer usage from the name alone.

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