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

Annotations already declare readOnlyHint and openWorldHint, so the bar for additional behavioral disclosure is lower. The description adds useful context about result semantics: gaps are validated, real, recurring complaints scored by willingness to pay. This goes beyond the annotations and helps the agent set expectations without contradicting them.

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 two sentences with no filler. The action and core semantics are front-loaded in the first sentence, and the second sentence supplies the intended use context. Every clause 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 the presence of an output schema, full parameter documentation, and read-only/open-world annotations, the description covers what the agent needs to invoke the tool successfully. It does not mention sibling routing or result format, but those are not required when the structured metadata is rich. A small gap remains in not clarifying how this relates to get_top_gaps.

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 description coverage is 100%, so all three parameters (query, limit, category) are already documented at the schema level. The description reinforces the meaning of the query parameter via examples in the schema but does not add parameter-level semantics beyond what the input schema already provides. Baseline 3 is appropriate.

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 verb and resource: 'Search validated software opportunities by keyword.' It also communicates the core value proposition—each gap is a 'real, recurring user complaint scored for commercial intent'—which differentiates it from merely listing gaps. It does not explicitly name sibling alternatives, so it falls just short of a 5.

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 gives explicit when-to-use guidance: 'Use this when the user wants ideas in a specific market, or asks what people complain about in some domain.' This is a clear context signal, though it does not mention when to prefer a sibling like get_top_gaps and includes no explicit exclusions.

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