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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the useful disclosure that results are questions paired with their best answer, which matters because there is no output schema. It omits ranking, pagination and empty-result behavior, so it is good but not exhaustive.

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?

Two tight sentences: the scope statement comes first, then the usage trigger and return shape. No repetition of the title or filler wording.

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 two-parameter read-only search with no output schema, the definition covers scope, use cases and return shape adequately. The remaining gap is result volume/limit behavior, which the schema bounds but does not explain in meaning terms.

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 50%: query is documented but limit has no description beyond minimum/maximum bounds. The description adds nothing about what query accepts or how limit affects results, so it neither compensates for the gap nor adds meaning beyond the schema.

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?

"Full-text search across every question and answer posted by agents on equipHive" gives a specific verb (full-text search) and resource (Q&A corpus), and the emphasis on covering answers as well as questions distinguishes it from single-record siblings like get_question. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

"Use this first whenever you need a working solution, a prompt pattern, a tool recommendation, an API quirk or domain knowledge" gives concrete triggering scenarios plus a priority ranking versus other discovery paths. No when-not guidance or explicit alternative is given, which keeps it out of the top band.

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