erc8004__import_feedback

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

The description mentions idempotency per feedback_id, which is a useful behavioral trait. However, it does not disclose authorization needs, side effects, or what happens on duplicate imports. With no annotations, more detail would be expected.

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 brief with two sentences and a structured list of item fields. It is front-loaded with the primary action. Could be slightly improved with parameter explanations but remains efficient.

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?

Lacks explanation for the chain_id and token_id parameters, no usage context, and no output schema. For a tool with 3 required parameters and complex feedback structure, the description is incomplete.

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 description details the fields within the feedback array items but does not explain chain_id or token_id parameters. With 0% schema description coverage, the description fails to compensate for missing parameter meaning.

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 imports ERC-8004 Reputation Registry feedback records for an agent, distinguishing it from sibling tools like import_registration and score_agent. It uses specific verb and resource.

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. It does not mention prerequisites or when not to use it, leaving the agent to infer from context.

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