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

With no annotations, the description carries the full burden; it does disclose the key behavioral traits that this is an onchain write and that it is gasless (Pabandi pays gas), which is genuinely useful. It omits idempotency (does re-syncing overwrite prior feedback?), reversibility, and latency/confirmation behavior for a chain write.

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?

Three short sentences, front-loaded with the action and target, then the payload, then the cost model. No filler and no repetition of the tool name.

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 an unannotated onchain mutation with no output schema, the description covers what is written and who pays gas, but leaves open the result of the call, whether prior reputation is appended or replaced, and any precondition on the passport. Adequate but with clear gaps.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines passportId. The description only indirectly implies passport scoping ('an agent's trust score') and adds no format or sourcing detail beyond the schema, matching the baseline 3.

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?

Specific verb+resource: syncs an agent's trust score to the onchain ERC-8004 reputation registry, and clarifies what is posted (task feedback and success rate). It is distinguishable from siblings like pabandi_trust_resolve or pabandi_verify_trust_attestation by the write-to-registry framing, though no sibling is named explicitly.

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?

'Posts feedback about completed tasks and success rate' implies the trigger is task completion, but there is no explicit when-to-use, no exclusions, and no mention of prerequisites such as an existing passport or prior identity registration.

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