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

With no annotations, the description is the sole source for behavioral disclosure. It reveals that the tool runs the profile through a matching engine and requires a complete profile, but it does not discuss side effects, error behavior, output shape, or any potential cost/limitation. This is adequate but minimal.

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 concise (two sentences) and front-loaded with the main purpose. However, it includes a redundant 'GrantIQ find_opportunities:' prefix and an unnecessary internal service name ('canonical StagedMatchingService'), which are minor distractions.

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-only tool with one parameter, the description offers the essential purpose and a key precondition. However, without an output schema, it leaves the result structure unspecified, and there is no mention of what happens if the profile is incomplete. It is minimally complete but not comprehensive.

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 single parameter 'limit' is fully described in the schema (100% coverage), so the description need not add more. The baseline of 3 applies because the schema already documents the parameter meaning.

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 runs the user's profile through an AI matching engine to find top grants, using a specific verb-resource pair. This distinguishes it from sibling tools such as search (likely keyword-based) and explain_opportunity (explains a specific grant).

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 includes an explicit prerequisite ('Requires a complete profile'), giving clear context for when the tool is appropriate. However, it does not explicitly name alternative tools or exclusions, so it lacks full when-to-use/not-use guidance.

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