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

With no annotations, the description carries the full behavioral burden. It discloses that the tool is read-only ('Return'), gives an approximate count ('~10'), and specifies the result types ('grants + contracts'). It does not explain how matching is determined, how ranking works, or what happens when optional parameters are omitted.

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 a single, efficient sentence that front-loads the action and result shape. It earns its place, though the brevity sacrifices useful behavioral and usage detail.

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?

An output schema exists, which covers return values, and the basic operation is clear. Still, the definition is incomplete for a tool that overlaps with several search-related siblings: it does not state when to prefer match_opportunities over search_awards, search_grants, or search_contracts, nor does it clarify the matching logic or optional parameter effects.

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 does not explain any of the three parameters. 'Org profile' loosely maps to org_description, but org_type and focus_areas are completely unmentioned, leaving the agent to rely on parameter names alone.

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 ('Return') and clearly identifies the resource ('grants + contracts') as well as the matching criterion ('matched to an org profile'). This distinguishes it from generic search tools, although it does not explicitly name sibling alternatives.

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 phrase 'matched to an org profile' implies the tool should be used when the agent has an organizational profile and needs tailored opportunities. However, it provides no explicit when-to-use/when-not-to-use guidance and does not mention the overlapping search_awards, search_grants, or search_contracts tools.

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