nexus_audit_repository_content

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine context beyond them: results are bounded by server-side caps, continuation tokens are handled internally and never returned, and any incomplete result carries explicit completion evidence that must not be used for retirement decisions. That is meaningful disclosure of truncation behavior.

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?

Three short sentences, front-loaded with the core action and followed by the two facts that matter most (token handling and the retirement-decision caveat). Little waste, though the line-broken formatting makes it slightly harder to scan than a single tight paragraph.

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?

An output schema exists and covers return values, so the description need not narrate the result shape. It supplies what the schema cannot: the server-side paging model, the meaning of completion evidence, and a hard constraint on downstream use. Combined with annotations, an agent has enough to call this 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?

Schema description coverage is 0%, so the description carries the full burden for the three parameters, and it does not. The word 'bounded' gestures at max_pages and max_components but never explains what those caps mean, what defaults do, or what format the repository identifier takes (name, id, path). Only a vague hint of truncation semantics is provided.

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 opens with a specific verb and resource: 'Collect a bounded complete repository component inventory server-side.' That is clearly a read/collection operation on repository content. It does not, however, distinguish itself from plausible siblings such as nexus_generate_inventory_json or nexus_generate_audit_report, so an agent must infer the boundary from the name alone.

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?

Usage is only implied: the note that 'incomplete results must not be used for retirement decisions' tells the agent what this data feeds into, and the 'bounded complete' phrasing hints at a paging-limited enumeration. There is no explicit when-to-use versus the inventory or catalog siblings, and no stated prerequisites for the repository argument.

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