trust__record_outcome

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

Only discloses one behavioral aspect (3x penalty for security incidents), but lacks details on side effects such as reputation updates, idempotence, or required permissions. With no annotations, the description carries the full burden and falls short.

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?

Description is short and front-loaded with the action. The bracketed module context is mildly extraneous but does not significantly detract.

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?

Missing information on return values, effect on reputation, and the role of parameters like weight and counterparty. Incomplete for a tool with 5 parameters and no annotations.

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?

Despite 0% schema coverage, only the 'kind' parameter is explained. Other parameters (agent_id, note, weight, counterparty) are not described, leaving their meaning and usage unclear.

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?

Description clearly states 'Record an interaction outcome for an agent.' with a list of possible kinds, distinguishing it from sibling tools like trust__attest or trust__score_agent.

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?

Provides no explicit guidance on when to use this tool versus alternatives, though the list of kind values implies common use cases.

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