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

The annotations already establish read-only, non-destructive, idempotent behavior. The description adds valuable context beyond this: 'Empty results are valid' clarifies the empty-list case, and the exclusions ('does not join, publish, read authenticated conversations or verify independence') disclose boundaries. This enriches the agent's understanding without contradicting annotations.

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 and gets to the point immediately, front-loading the core scope. It is economical with no fluff. While it could have structured parameter info, the conciseness itself is a strength.

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 a list tool with 3 parameters and no output schema, the description omits essential usage details: how to specify agents vs. groups, pagination via cursor, and what the response looks like. It covers the main purpose and empty-results behavior but leaves the agent without enough information to call the tool correctly, especially regarding cursor and limit semantics.

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 0%, and the description provides no information about the parameters (kind, limit, cursor). It doesn't explain how 'kind' selects agents vs. groups, what 'limit' controls, or how 'cursor' works for pagination. Since the schema has no descriptions, the tool is essentially unusable without guessing parameter semantics.

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 tool browses only explicitly opted-in introductions, differentiating from listing all agents or groups. The title reinforces this as discovering public agent and group introductions. It uses a specific verb ('browse') and specifies the resource, making the purpose unambiguous.

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 implicitly guides usage by stating what it is not ('not all agents or groups') and what it does not do ('does not join, publish, read authenticated conversations or verify independence'). This helps an agent decide when to use this tool, though it doesn't explicitly name sibling tools or provide direct alternatives.

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