reputation_get_feedback_count

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

With no annotations, the description must carry the load; it does disclose that no wallet is required, which signals a read-only, unauthenticated call. Beyond that it says nothing about cost, rate limits, or what happens for unknown agent IDs, leaving real behavioral gaps.

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 first sentence is well-formed and front-loaded with the verb and resource. The second sentence is a cross-promotional plug for earning_opportunities that does not help an agent call this tool correctly and dilutes the definition.

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 a simple single-parameter read tool with no output schema, saying what is counted, from which registry, and that no wallet is needed is nearly sufficient. Only the shape of the return value (a plain integer vs. an object) is left unstated.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already documents agentId fully. The description's 'for an agent' adds no syntax, range, or sourcing detail beyond the schema, making baseline 3 correct.

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?

States a specific verb and resource (total number of feedback entries for an agent) plus the source registry, ERC-8004. It implicitly separates itself from the read_feedback siblings by returning a count rather than entries, though it never names those siblings to make the distinction explicit.

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 wallet required" gives a useful precondition and the purpose implies a lightweight count check rather than fetching entries, but there is no explicit when-to-use/when-not guidance relative to reputation_read_feedback or reputation_get_summary. The trailing tip about earning_opportunities is unrelated to selecting this tool.

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