get_newsGet Nexus Mods news updates, filtered by game or category. Specify a game domain, category, and count to retrieve relevant news items.
Latest Nexus Mods news, optionally per game/category.
| Name | Required | Description | Default |
|---|---|---|---|
| game | No | Game domain name, e.g. "skyrimspecialedition" | |
| count | No | ||
| category | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already convey the safety profile with readOnlyHint and idempotentHint, so the description does not need to repeat that. It adds minimal behavioral context by saying 'Latest' (implying chronological ordering) and 'optionally per game/category' (indicating filtering behavior), but it does not disclose return format or pagination. No contradiction exists.
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 a single nine-word sentence that is front-loaded and free of filler. Every word adds meaning, making it highly scannable and efficient for an agent to parse.
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?
With three optional parameters and no output schema, the description omits count semantics, fails to clarify the category enum values, and offers no usage guidance. Annotations cover safety, but an agent still must guess at count behavior and expected return shape, making the description incomplete for confident invocation.
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 description coverage is only 33%, and the description merely mentions 'per game/category' without explaining the count parameter or the meaning of category enum values. It partially compensates for game and category but leaves count's role as the number of news items to inference, so it does not adequately cover the low schema coverage.
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-resource pair: it retrieves 'Latest Nexus Mods news' with optional filters 'per game/category'. It is clearly distinguishable from sibling tools because none of the other siblings target news, and the title 'Get News (GraphQL)' reinforces the dedicated purpose.
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 provides no guidance on when to use this tool versus alternatives such as the generic graphql_query or list_mods. It only states what the tool does, without explicit context, prerequisites, or exclusion conditions, leaving the agent to infer when it should be selected.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.