spruthub_list_methods

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the tool lists methods and includes categories/descriptions, but does not mention that it is read-only, whether there is pagination, or how filtering behaves for invalid categories. It adds only the basic facts without deeper context.

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 sentence that is front-loaded with the action ('List') and resource. Every word adds value: 'all', 'available', 'categories', 'descriptions'. There is no fluff or 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?

For a simple list tool with one optional filter and no output schema, the description adequately explains what the tool returns (methods with categories and descriptions). It could mention that this is the starting point before using get_method_schema or call_method, but given the simplicity, it is nearly complete.

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% for the single optional parameter 'category', which already explains its purpose and allowed values. The description adds no parameter-specific information, so it neither improves nor detracts from the schema. Baseline 3 is appropriate.

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 'List', the resource 'Sprut.hub JSON-RPC API methods', and the scope 'with their categories and descriptions'. It distinguishes itself from sibling tools (get_method_schema and call_method) by focusing on enumeration rather than details or invocation.

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 clear context: this tool lists all available methods. While it doesn't explicitly mention when to use it over siblings, the purpose is self-evident as a discovery/listing tool. There are no exclusions or alternative recommendations, but the context is clear enough for an agent to select it appropriately.

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