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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful cost semantics (compact is token-cheap, full is heavy), but says nothing about pagination behavior, result caps, or what happens with an empty query — the main behavioral unknowns left.

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, front-loaded with the purpose and followed by the single most consequential decision (mode). Nothing is padded and no sentence merely restates the tool name.

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 read-only, 6-parameter, all-optional search tool with no output schema, the description covers the key routing decision and cost trade-off. It could note result-size or pagination expectations, but the rich schema already carries parameter detail.

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% and the schema itself documents mode, sortBy, starredOnly, page, and limit thoroughly, so the baseline is 3. The description reinforces the mode default and its cost trade-off, which is the parameter most likely to be misused, but adds no syntax or field-level detail 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?

States a specific verb+resource ("Search/filter Convocore agents") and immediately differentiates itself from both siblings: list_agents for recent agents without a query, and get_* for single items. An agent can route correctly from this sentence alone.

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?

Gives explicit conditional guidance: default mode=compact, use mode=full only for complete agent docs, and prefer list_agents when there is no query. Both the when and the alternative are named rather than inferred.

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