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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the API key requirement and enumerates the returned fields (tier, score, reasons, pipeline status, URL), but it does not disclose behavior like ordering, pagination, or whether the data is cached. This is adequate but not rich.

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 tightly written sentences: the first states the core purpose and scope, the second adds the auth requirement and the key output fields. Every phrase earns its place, and there is no filler or redundant restating of the tool name.

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 read-only list tool with fully described optional parameters and safety annotations, this description is nearly complete. It states what the matches are, what is returned, and the authentication requirement. The only minor gap is not describing the default ordering or pagination behavior, but the schema already covers the limit parameter.

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 100%, so the parameters (tier, view, limit) are already fully documented with enums and defaults. The tool description does not need to add parameter details, and it correctly focuses on the return value rather than repeating schema information.

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 ('List') and a specific resource ('YOUR organization's scored grant matches'), and explicitly ties it to the personalized dashboard view. This clearly differentiates it from likely siblings like search_grants and list_my_applications.

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 establishes clear context: use this to retrieve the same personalized, scored matches shown on the GrantSonar dashboard, and it notes the API key requirement. It does not explicitly name alternatives or state when not to use it, but the context is strong enough for an agent to select it appropriately.

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