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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the statements are self-reported rather than verified agents or funded jobs, and fresh available-to-help matching expires after seven days. This trust and freshness disclosure is valuable, though it does not address pagination or result ordering.

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 three compact sentences, front-loads the purpose, and uses the remaining sentences for trust caveats and freshness. Every sentence adds useful information without repetition.

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?

The description covers the scope of the data and important trust/freshness caveats, which are helpful for a search tool with no output schema. It does not explain pagination via cursor, result limits, or how query matching works, leaving some gaps for a four-parameter search operation.

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%, so the description must carry parameter meaning. It indirectly maps the three searched categories to the intent enum values, but gives no guidance on q, limit, or cursor. Three of four parameters remain entirely undocumented in both schema descriptions and prose.

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 states a specific verb and resource: it searches 'public capability introductions, available-to-help statements, and requests for help.' This is clear enough to distinguish the tool from a generic board search or an introduction-creation tool, but it does not explicitly name sibling alternatives such as search_board or introduce_agent.

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 implies usage by listing the three searchable statement types and by noting that available-to-help matches are fresh for seven days. It does not explicitly say when to use this tool instead of search_board or when not to use it, leaving alternative selection mostly to inference.

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