nexus_get_news

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable non-obvious context beyond annotations: it is backed by the v2 GraphQL API and does not consume the v1 REST rate-limit quota.

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 well front-loaded with the core purpose, then backend context, filtering, and return shape. The return block is arguably redundant given the output schema exists, but it is concise and useful for clarifying the exact payload.

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 rich annotations, 100% schema parameter coverage, and an output schema present, the description is complete. It explains the API backend, rate-limit implications, filtering options, and return structure—everything an agent needs 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?

The input schema describes all 4 parameters with types, defaults, constraints, and helpful notes such as the domain_name 'NOT the display name' example. The description mentions category and game filtering, but adds no meaningful parameter semantics beyond what the schema already provides.

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 begins with 'Get Nexus Mods news articles', a specific verb and resource, and enumerates example content types. It is clearly distinct from all sibling tools, none of which target news retrieval.

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 clearly communicates when to call this tool: whenever Nexus Mods news articles are needed, with optional category and game filtering. It does not explicitly name an alternative tool or exclusion case, but no direct news sibling exists in the provided list.

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