parliament_tracker

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

No annotations are provided, so the description must carry the full burden. It only says 'Track... DEMO' without disclosing whether operations are read-only, any authentication needs, rate limits, or what happens on use. The 'DEMO' label is ambiguous.

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 extremely short (one sentence) but lacks essential details. It does not earn its place by providing key information beyond a minimal statement of purpose. Front-loading is not relevant when content is so sparse.

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?

Given the lack of annotations, a single undocumented parameter, and only a minimal purpose statement, the description is wholly inadequate. An output schema exists but is not described. The tool as defined does not provide enough information for an agent to use it correctly.

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 input schema has one required parameter (query_type) with no description or enum. Schema description coverage is 0%. The description does not explain what values query_type accepts or how it relates to the listed items (bills, etc.).

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 clearly states the tool's purpose: tracking Kenya parliament with specific entities (bills, Hansard, committees, petitions). It distinguishes from sibling tools which cover citizen feedback, gazette, open data, and tenders.

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, nor any context for when it is appropriate. The description only lists what it tracks, with no mention of prerequisites or exclusions.

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