nexus_get_tracked_mods

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context by stating the requirement for an authenticated account and by specifying the exact return shape ('JSON array of {mod_id, domain_name}'). This goes beyond what annotations provide and contains no contradiction.

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 extremely concise: a single sentence stating the core action followed by a one-line return format. The purpose is front-loaded, and every word earns its place. No redundant or vague phrasing.

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, read-only list tool, the description fully covers what it does and what it returns. It mentions the authentication requirement and the output structure. An output schema exists to further document the return value, so nothing essential is missing for an agent 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 tool has zero parameters, and the input schema is empty. Per rubric, the baseline for zero parameters is 4. The description appropriately omits parameter details since none exist, so no additional semantic clarification is needed.

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 clearly states a specific verb ('List') and resource ('mods the authenticated account is tracking'). It distinguishes the tracking scope from generic mod list endpoints like nexus_get_trending or nexus_get_latest_added, but does not explicitly contrast with closely related siblings such as nexus_get_opted_in_mods, which could be confused for a similar list.

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. It does not mention exclusions, prerequisites (other than inherent authentication), or when a different listing tool would be more appropriate. The agent must infer usage purely from the name and sibling context.

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