spruthub_call_method

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

No annotations are provided, so the description bears the full burden. It discloses the prerequisite schema requirement and warns against guessing, but does not mention potential side effects, return value, or error behavior of executing arbitrary methods. This is partial 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?

The description is three short sentences, with purpose stated first and critical warnings highlighted with 'IMPORTANT.' Every sentence earns its place, and there is no redundant 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?

As a generic executor, the description provides the essential workflow (call schema first) and is complemented by sibling tools for listing and schema retrieval. It omits return value and error details, but these are likely found via the method schema, so the description is adequate if not exhaustive.

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 description coverage is 100%, with both 'methodName' and 'parameters' clearly documented, including examples and the requirement to consult the schema. The tool description adds no new parameter semantics beyond reinforcing the same instructions found in the schema.

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 'Execute any Sprut.hub JSON-RPC API method' with a specific verb and resource, distinguishing it from sibling tools like spruthub_list_methods and spruthub_get_method_schema. It is unambiguous about the tool's role.

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?

Explicitly instructs 'You MUST call spruthub_get_method_schema first' and 'Never guess parameters,' giving clear when-to-use and when-not-to-guess guidance. This is directly actionable for an agent.

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