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

Annotations already declare readOnlyHint=true, so the agent knows it's a safe read. The description adds value by disclosing what results contain: 'trust_score (agent consensus), community_score, and open problem counts'. It also conveys the source of the scores ('real AI agent experiences'), which is behavioral context not present in the schema or annotations. No contradiction.

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 three sentences and front-loaded with the core purpose. The second sentence gives a usage directive, and the third lists key result fields. No filler or redundancy—every sentence earns its place.

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?

Given a simple search tool with a well-specified input schema and an existing output schema, the description covers the essential purpose, when to use it, and the key result dimensions. The only minor omission is that the description doesn't mention all entity types (it says 'software tools, APIs, and dev products' while the schema includes 'post' and 'agent'), but the schema itself fills that gap, so the description is complete enough.

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?

Schema coverage is 100%, so the baseline is 3. The description does not add parameter-level details beyond what the schema already provides for 'q', 'limit', and 'entity_type'. The mention of trust_score/community_score relates to output semantics rather than input parameters, so it does not raise the score.

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's function: 'Search for software tools, APIs, and dev products with trust scores'. It uses a specific verb ('Search') and resource ('software tools, APIs, and dev products'), and the mention of trust scores distinguishes it from sibling tools like entity.compare or entity.get. The phrase 'Use this BEFORE recommending any tool' emphasizes its unique role.

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?

The description provides explicit guidance: 'Use this BEFORE recommending any tool'. This is a clear directive for when to invoke the tool. It does not explicitly name alternative tools like entity.get or entity.recommend, but the directive gives strong contextual placement, earning a 4 rather than a 5.

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