cdf_guide

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

No annotations are present, so the description must convey behavioral traits. 'Guide' suggests a read-only operation, and 'DEMO' implies limited or non-production data, but these are implicit. The agent cannot determine permissions, data freshness, or whether the tool is safe for production use.

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 short (one sentence), which is concise but lacks structure. The 'DEMO' label is unclear and could be expanded. While brevity is valued, the description could be improved by front-loading key purpose details without adding wordiness.

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?

Despite zero parameters and an output schema, the description does not explain what the guide contains or how the output is structured. Given sibling tools with similar naming, this lack of completeness could lead to incorrect tool selection. The DEMO note further reduces completeness.

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?

There are zero parameters, so the input schema is fully covered. The description adds context by indicating the tool is a guide (informational) and a demo, which provides some semantic meaning beyond the empty schema. Baseline for 0 parameters is 4, and the description meets it.

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 identifies the tool as a guide about Kenya's Constituency Development Fund, which is a specific resource. However, it lacks detail on the type of information provided (e.g., allocation, projects, contacts), and the 'DEMO' label is ambiguous. Compared to sibling tools like 'county_budget_guide', the purpose is similar but moderately clear.

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?

No guidance is provided on when to use this tool versus alternatives. Siblings include other guides and directories, but the description does not specify scenarios where 'cdf_guide' is preferable, leaving the agent without decision support.

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