summitflow_resources

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the content type ('templates, guides and calculators') and location ('on the web') but fails to mention whether this is a live fetch, a static list, how results are returned, or any network dependencies. The agent is left with no behavioral insight.

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 very concise, but it is under-specified. It is a single sentence without a verb or clear structure. While brevity is positive, it borders on a label rather than a functional description, so it does not fully earn its place.

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?

The tool has an output schema but no annotation context. The description does not explain what the tool returns or how the output relates to the mentioned templates/guides/calculators. For a resource tool, the agent needs to know whether the output is a list of links, metadata, or downloadable files, but this is entirely absent.

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 has zero parameters, and the schema is empty. Per the rubric, a baseline of 4 is appropriate for zero-parameter tools. The description correctly does not attempt to explain parameters since there are none.

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 'Free grant templates, guides and calculators on the web' is a noun phrase without an explicit verb or action. It hints at the resource type but does not clearly state what the tool does (e.g., lists, retrieves, or provides these items). It is not a tautology but lacks a specific functional purpose.

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 provides no guidance on when to use this tool versus the sibling tools (e.g., grant_budget, volunteer_time_value). There is no mention of use cases, prerequisites, or alternatives, leaving the agent to infer applicability.

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