describe_rpc_command

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

No annotations are provided, so the description carries the full burden. It discloses the return structure (description, arguments, examples) but does not confirm if the operation is read-only, cached, or requires network connectivity to the Bitcoin node. The phrase 'Get structured help' suggests a safe read operation, but this is not explicit.

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?

Efficiently structured with the purpose in the first sentence followed by an 'Args:' section documenting the parameter. No wasted words, though the 'Args:' formatting is slightly informal. Front-loaded with the most critical information.

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?

Appropriate for a single-parameter tool with an output schema (not shown). The description previews the output structure (description, arguments, examples) which aligns with the existence of an output schema, making the overall documentation sufficient without being verbose.

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?

With 0% schema description coverage (only title 'Command' provided), the description adds essential semantic meaning: 'RPC command name' and concrete examples. This effectively compensates for the schema's lack of documentation, though it lacks format constraints or validation rules.

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?

Clearly states the tool retrieves 'structured help for a Bitcoin RPC command' including description, arguments, and examples. However, it does not explicitly differentiate from sibling tool 'list_rpc_commands' (which lists available commands versus describing specific ones).

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?

Provides concrete examples ('getblock', 'sendrawtransaction') that imply when to use the tool, but lacks explicit guidance on when to prefer this over external documentation or direct RPC execution. No 'when-not-to-use' guidance is provided.

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