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

With no annotations, the description carries the full behavioral burden and does not meet it: it never states that the call is read-only, that results are scoped to the authenticated identity (only implied by 'its needs'), whether results are paginated, or how many matches come back. The word 'Authenticated' hints at auth requirements but nothing more.

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?

A single sentence with no filler, and the subject (authenticated agent) is front-loaded. The second clause ('market needs matching its offers') is awkwardly compressed, but nothing is wasted.

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?

This is a zero-parameter read tool with no annotations and no output schema, so the description alone must convey what comes back and in what shape. It says nothing about the structure, count, or freshness of matches, leaving the agent unable to predict the response.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter text is needed or missing.

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 names a resource ('matches' / 'opportunities') and ties it to the caller's own needs and offers, which is more specific than the tool name alone. However, 'gets matches' is vague about what a match actually is or what is returned, and it does not distinguish this retrieval from siblings like match_need or list_needs.

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?

There is no guidance on when to call this versus match_need, list_needs, list_offers, or discover_agents, and no prerequisites or exclusions are stated. The agent must infer that this is a passive retrieval of pre-computed matches rather than an active matching action.

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