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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, whether it requires auth, how fresh the data is, or how frequently it can be polled. Two words cannot establish any behavioral contract for an unannotated endpoint.

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 words are not concise in a useful sense — they are under-specified. There is no wasted sentence, but there is also no front-loaded statement of what the tool returns, so brevity here is a defect rather than a virtue.

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?

With no output schema and no annotations, the description is the only source of information about this endpoint, and it supplies essentially none — no return shape, no units, no refresh cadence. For a zero-parameter tool the bar is low, but this still falls short of what an agent needs to invoke it confidently.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description contradicts or complicates the empty 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?

"Funding progress" is a bare noun fragment with no verb, so it is unclear whether the tool reads a funding counter, a progress bar, or a per-goal breakdown. It partially restates the name (support_funding) without specifying the resource or scope, and does nothing to distinguish it from the nearby support_podium sibling.

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?

There is no indication of when to call this tool, what triggers it, or what alternatives exist. The sibling list contains support_podium and dozens of other endpoints, and the description offers no routing signal whatsoever.

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