get_roadmap

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

No annotations are provided, so the description must compensate. It only states the tool's purpose but does not disclose whether it is read-only, has side effects, or requires special permissions. The word 'Starter tier' hints at limitations but is insufficient.

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 (one sentence), but it lacks substantive details. It is front-loaded with key terms but could be expanded to include more information without losing conciseness.

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 no output schema and a simple input schema, the description should explain what the roadmap includes, how the fact-check affects results, and the meaning of 'Starter tier.' It does not provide enough context for complete understanding.

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 schema description coverage is 100% for the single parameter entity_slug, which has a clear description. The tool description does not add any additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 'Project roadmap with BCA editorial fact-check. Starter tier.' indicates the tool retrieves a project roadmap with editorial fact-checking, which aligns with the name. However, it lacks specificity on the exact content and does not distinguish from sibling tools like get_article or get_explainer.

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 on when to use this tool over alternatives. With many sibling tools, the agent needs explicit context about appropriate scenarios, prerequisites (e.g., having an entity_slug), and when not to use it.

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