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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context by warning that legacy imports may include test data and that unverified imports are not verified live opportunities, which is not captured in the 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?

Two concise sentences with no filler. The core purpose is front-loaded, and the data quality caveat is placed in the second sentence without bloating the description.

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 simple read operation with one optional parameter, the description is largely complete and includes an important data quality warning. It could be slightly more explicit about how this relates to searching or profiling opportunities, but nothing critical is missing for basic invocation.

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 only parameter, 'limit', is fully specified in the schema with type, default, minimum, and maximum, so the description does not need to add much. However, schema description coverage is 0% and the description does not mention 'limit' at all, though its meaning is self-evident from 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?

The description uses a specific verb and resource ('Read stored opportunity matches'), clearly stating what the tool does. It differentiates somewhat by saying 'stored' matches, implying persistence, but it does not explicitly distinguish itself from siblings like helvabase_search_opportunities or helvabase_opportunity_profiles.

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?

No guidance is provided on when to use this tool versus alternatives such as helvabase_search_opportunities or helvabase_opportunity_profiles. The data quality caveat about legacy imports is useful but does not help an agent decide between this and other opportunity-related tools.

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