nexus_get_trending

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful context about the fixed count of 10 and the trending scope, while also noting the array return shape, but it does not discuss auth, rate limits, or other operational behavior 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 sentence that front-loads the action and scope, with no filler or repetition. Every word contributes to the agent's understanding.

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 single-parameter read-only tool, the combination of the description, full schema documentation, annotations, and output schema is sufficient. The agent can correctly invoke it with a game domain and understand the result shape without additional context.

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 100%, and the schema already explains domain_name with examples and the explicit 'NOT the display name' warning. The tool description only adds 'for a game', which adds no meaningful parameter semantics 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?

States a specific verb and resource: 'Get the 10 currently trending mods for a game'. It also clarifies the return shape as an array of mod info objects, and the trending scope distinguishes it from sibling tools like nexus_get_latest_added or nexus_get_latest_updated.

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 this tool is for retrieving currently trending mods for a given game, but it does not explicitly say when to prefer it over similar read tools such as nexus_get_latest_added, nexus_get_latest_updated, or nexus_search_mods. No exclusions or alternative routing guidance is provided.

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