Extract a Daily Kos staff article's title, author, publication time, and readable body paragraphs from its canonical /news/ URL; community stories and images are excluded.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Daily Kos staff /news/ article URL |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Input schema / properties / url / descriptionAdded value: +"Canonical Daily Kos staff /news/ article URL"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint, openWorldHint). The description adds real scope intelligence: only staff /news/ articles are supported, community stories and images are stripped. That is meaningful behavioral context beyond the annotations.
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?
A single front-loaded sentence that leads with the verb and outcome, then appends the scope exclusions. No filler or redundant sentences.
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?
An output schema exists, so return-value shape need not be explained, and the description still names the extracted fields. Combined with the staff-only/community-stories exclusion, an agent has everything needed to invoke 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?
Only one parameter with 100% schema description coverage; the schema already states 'Canonical Daily Kos staff /news/ article URL.' The description merely restates the canonical /news/ constraint, adding no syntax, format, or validation detail beyond the schema.
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?
Uses a specific verb (Extract) and resource (Daily Kos staff article) and enumerates exactly what is returned: title, author, publication time, and body paragraphs. It also draws a clear boundary against 'community stories and images,' so an agent can distinguish it from sibling listing tools like dailykos_headlines and dailykos_news.
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 phrase 'from its canonical /news/ URL' and the exclusion of community stories imply the correct usage context (a single known article URL, not a feed or search). It stops short of naming alternatives such as dailykos_headlines for discovery, so it lacks explicit routing.
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.