List Vox editorial sections with slugs, display names, and URLs. Use the slugs as section values for vox-headlines.
Get Vox sections. Lists the Vox editorial sections accepted by vox-headlines, each with a stable slug, a display name and the section url. Use the slugs as the section value. Takes no parameters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden and does disclose that the tool takes no parameters and returns structured fields (slug, name, url) from a stable enumeration. It does not restate read-only semantics explicitly, but for a no-arg listing the safety profile is unambiguous from 'Get/List'.
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?
Four short sentences, front-loaded with purpose, then field detail, then the critical usage instruction, then the no-parameter note. Every sentence earns its place with no padding.
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 zero-parameter, annotation-free lookup with no output schema, the description supplies everything an agent needs: what it returns (slug, name, url) and how to apply the result. Nothing relevant is missing.
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 baseline is 4; the description correctly states 'Takes no parameters,' removing any ambiguity. There is nothing further to document.
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 states a specific verb and resource ('Get Vox sections. Lists the Vox editorial sections') and scopes it precisely as the set accepted by `vox-headlines`. This distinguishes it cleanly from siblings like vox_headlines, vox_news and vox_article without the agent needing to open any schema.
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?
It explicitly names the consuming tool (`vox-headlines`) and instructs 'Use the slugs as the `section` value,' which is clear when-to-use guidance. It stops short of stating any when-not condition or alternative lookup source, so it does not reach the 5 bar.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.