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

No annotations are provided, and the description only states that feedback is submitted. It fails to disclose behavioral traits such as idempotency, authorization needs, rate limits, or whether feedback can be modified or deleted.

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, which is concise, but it sacrifices valuable information. It is not optimally structured for clarity; the phrase 'positive or negative' could be replaced with specific parameter details.

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?

The tool has 5 parameters (4 required), including a nested evidence object and no output schema. The description is far too minimal—it omits input format, return values, and behavior, making it inadequate for correct invocation.

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?

With 0% schema description coverage, the description adds almost no parameter context. It mentions 'positive or negative' but does not map this to the rating parameter (integer -2 to 2). No explanation of subjectType, category, or evidence.

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 action (submit feedback) and the resource (agent/wallet) and mentions positive/negative feedback. However, it lacks differentiation from sibling tools like agent_trust_batch (batch submission) and agent_trust_score (querying score).

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?

No guidance on when to use this tool versus alternatives. The description does not mention batching or scoring, leaving the agent without decision context.

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