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

With no annotations, the description carries the full behavioral burden. It adds the 'verified' qualifier, which hints at data trustworthiness, but discloses nothing about return format, pagination, caching, or freshness. The safety/mutation profile is trivially inferable (a read), but other behavioral traits are absent.

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 front-loaded sentence with the verb first and no filler. Slightly adjective-heavy ('sports, community, and environmental'), but each qualifier narrows scope usefully.

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?

Low complexity (2 optional params, no output schema, no nested objects), and the purpose is conveyed. However, with no output schema and no return-value explanation, the agent can't anticipate what a 'funding stream' record looks like or whether results are ranked or filtered.

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 coverage is only 50%: max_budget_gbp is documented in the schema while project_type's five enum values are not explained. The description mentions none of the parameters, so it does not compensate for the coverage gap or clarify what 'all' returns versus a specific project_type.

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?

States a specific verb ('Retrieve') and resource ('grant funding streams') scoped to UK sports, community, and environmental funding for disc golf. This cleanly separates it from guidance/framework/policy siblings, though it never names a sibling to reinforce the distinction.

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 implies usage (get funding for course installation, equipment, club development) but gives no explicit when-to-use, prerequisites, or alternative tools. It does not tell the agent when to prefer this over, say, get_course_development_framework or get_club_starter_guidance.

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