get_storiesList current story bundles tracking ongoing policy issues. Returns a feed of active stories grouping related policies and developments.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of stories |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description confirms read-only with 'List' and 'Returns a feed'. It adds some context about the feed being active stories grouping policies, but doesn't detail pagination or output structure. No contradiction.
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 sentences, front-loaded with the purpose, and no filler. Every sentence contributes to understanding the tool.
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?
For a simple read-only tool with one optional parameter and no output schema, the description covers purpose, scope, and what is returned. It could mention explicit pagination or feed behavior, but overall it's complete for its simplicity.
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?
Schema coverage is 100% with the 'limit' parameter described as 'Number of stories'. The description doesn't add extra parameter semantics, but with full schema coverage the baseline of 3 applies.
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 uses the specific verb 'List' and identifies the resource as 'story bundles', adding scope with 'tracking ongoing policy issues' and 'active stories grouping related policies and developments'. This clearly distinguishes it from siblings like get_story (singular) and search_policies.
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 implies usage for viewing current, active story bundles related to ongoing policy issues. It doesn't explicitly state when not to use or name alternative tools, but the context is clear enough for an agent to differentiate from get_story.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: efforts, members, policies, stories, representatives, voter info, and text retrieval. Even similar tools like get_effort and resolve_effort clearly differ in input type (ID vs natural language), and get_stories vs get_story follow the standard list/detail distinction.
All tool names follow a consistent verb_noun pattern using lower_snake_case: get_ for retrieval, search_ for queries, and resolve_ for name resolution. Nouns are clear and descriptive, with no mixing of styles or inconsistent verbs.
With 12 tools, the set is well-scoped for a U.S. political policy tracking service. Each tool provides a distinct utility without overwhelming the surface, fitting solidly within the expected range.
The tool surface covers the core read-only workflows: searching and retrieving policies and members, resolving and retrieving efforts, listing and retrieving story bundles, and looking up representatives and voter info. There are no obvious gaps or dead ends for the stated purpose.