record_interaction

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

With no annotations provided, the description carries the full disclosure burden. It usefully reveals that submitted data feeds a shared, persistent 'reputation dataset for the community' – which implies public visibility of the write. However, it says nothing about required permissions, whether records are immutable, deduplication, or rate limits.

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 short sentences, zero filler, purpose front-loaded in the first clause. Nothing to trim.

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?

This is a 7-parameter mutation tool with no annotations and no output schema, so the description must carry more weight. It omits what happens after submission, whether the call can fail on validation, and what the response contains – important for an agent deciding whether to invoke it.

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?

7 parameters with only 57% schema description coverage, and the description adds no parameter-level meaning at all. Enum-constrained fields (source, outcome, target_type) are self-documenting in the schema, but 'source' in particular has no description anywhere and the description does nothing to compensate for the undocumented fields.

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 states a specific verb and resource ('Record an interaction with an agent, tool, or service'), which is unambiguous. It does not differentiate from the sibling tools (get_lowdown, compare_tools, get_node_stats), but those serve clearly different functions, so confusion risk is low.

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?

'after using it' gives implied timing guidance – call this once you have finished consuming a target. There is no explicit statement of when not to use it, no mention of prerequisites, and no comparison to alternatives.

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