block_raw_prevout_get

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

With no annotations, the description must disclose behavioral traits. It states it returns 'full decoded representation' and 'extensive details', but does not mention read-only nature, potential size of response, authentication needs, or performance implications. Adequate but lacking full transparency.

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?

Two sentences, front-loaded with purpose, no filler. Every sentence adds value without 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 complexity (Bitcoin block with prevout), no output schema, and sparse param description, the description could elaborate on what 'prevout information' includes or the structure of the response. It does not reference output schema or provide enough detail for an agent to fully understand the tool's capabilities.

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 only parameter 'identifier' has 0% schema coverage. The description adds that the identifier can be 'by its hash or height', which provides crucial context beyond the schema. However, it does not specify format or constraints like length or encoding, limiting full semantic clarity.

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 'Get', the resource 'full decoded representation of a specific Bitcoin block', and distinguishes it by 'with prevout information'. This differentiates it from sibling tools like block_raw_decoded_get or block_raw_summary_get.

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 implies usage when prevout data is needed, but does not explicitly state when to use this tool over siblings like block_raw_decoded_get. No direct guidance on when not to use or alternatives is provided, leaving room for ambiguity.

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