infer

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

Discloses return values (completion, node id, hash). No side effects mentioned, but inference is likely read-only. Without annotations, the description reasonably informs the agent of what to expect.

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: first states action and return, second provides alternative. No wasted words, front-loaded with the core purpose.

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 tool with two parameters and no output schema, the description covers the return value and usage context. Lacks discussion of errors or limits, but adequate for typical use.

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 coverage is 50% (only "model" has description). Description adds no further explanation for "prompt" or beyond schema. Fails to compensate for the missing parameter documentation.

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 verb ("Run"), resource ("ParalleliX network"), and singles out results ("completion plus serving node id and Proof-of-Execution hash"). Explicitly distinguishes from sibling "parallel_map" for bulk work.

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 states when to prefer alternative ("For bulk independent work, prefer parallel_map"), implying this tool is for single prompts. No additional prerequisites or context, but clear enough for simple usage.

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