mindgap_find

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

With no annotations, the description must disclose behavior. It mentions returns results + count and limit range, but lacks details on search behavior (e.g., exact vs fuzzy, case sensitivity, or what fields returned). No contradictions.

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?

One sentence, very concise and front-loaded with purpose. Could add more detail without being verbose, but acceptable for brevity.

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?

No output schema, no annotations, and only 0% parameter coverage. Description omits return format details (just 'results'), and doesn't clarify search behavior. Incomplete for effective use.

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 0%, so description should explain each parameter. It mentions 'query/type/tag' and limit with bounds, but does not define what query, type, or tag mean. The limit is well-documented, but the others are unclear.

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 it searches nodes by query, type, and tag, and returns results with a count. This distinguishes it from sibling tools that add, get, remove, or link nodes.

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?

It implies use for searching/finding nodes, but does not explicitly state when to use this versus alternatives like mindgap_get_node or mindgap_stats. No when-not or alternative tool guidance.

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