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

No annotations are present, so the description carries the burden. It adds useful behavioral context about required auth mode and the on-chain nature of the operation. However, it does not disclose side effects, transaction costs, confirmation behavior, or return values, so transparency is only partially addressed.

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 two tight sentences, front-loaded with the core action and followed by the critical auth caveat. There is no filler or repetition.

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 9-parameter, no-output-schema on-chain submission tool, the description conveys the core selection and auth facts but omits expected return/confirmation, on-chain effects, and usage caveats. The input schema covers parameters well, yet the description is not fully complete for safe invocation of a state-changing operation.

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 input schema covers all parameters, so the baseline is 3. The description adds meaning beyond the schema by clarifying that apiKey must be a worker feedback key rather than a wallet session token, and by constraining network to ERC-8004 or Solana-8004. This helps the agent map parameters correctly.

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 tool submits reputation feedback on-chain for ERC-8004 or Solana-8004 via the worker feedback route. This is a specific verb+resource and clearly distinguishes it from sibling tools, none of which handle feedback submission.

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?

It specifies the intended context ('worker feedback route') and a critical prerequisite (separate worker feedback API key, not a wallet session token). It does not explicitly discuss alternatives, but no sibling tool performs feedback submission, so the guidance is clear enough for when to use it.

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