search_agents

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is low. The description adds real behavioral context with the cost tradeoff (compact = token-cheap, full = heavy, prefer get_* for one item). It doesn't mention result-count or pagination behavior, but the page/limit params cover that.

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?

Three short sentences, zero preamble, with the core purpose and the mode default front-loaded before the alternatives. 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?

For a 6-param, all-optional read-only search with no output schema, the description plus full schema coverage is nearly complete. A brief note on what a compact result set contains (fields, pagination envelope) would close the remaining gap.

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% with per-param descriptions for every field including mode, sortBy, and starredOnly, so the schema carries the load. The description reinforces only the mode parameter's semantics; it adds nothing about search-query matching or sort behavior beyond the schema. Baseline 3 applies.

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 ("Search/filter Convocore agents") and immediately frames the default behavior (mode=compact returns short fields). It also names the siblings it must be distinguished from (list_agents, get_*), so an agent can route without opening a schema.

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?

Explicit when-to-use: mode=full only when complete agent docs are needed. Explicit alternative: prefer list_agents (compact) for recent agents without a query. It also defers single-item retrieval to get_* via the schema's mode note, covering all three paths.

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