nexus_explain_repository

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the scope of the explanation (storage, groups, cleanup policies) but says nothing about auth prerequisites, whether the explanation is derived from live or declared state, or how it differs behaviorally from the audit siblings.

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 front-loaded sentence with no filler and immediate scoping after the colon. It is efficient, though the terseness leaves gaps that a few more words could have closed.

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?

The tool is simple (one required parameter) and has an output schema plus annotations, so much of the burden is offloaded. Still, with zero schema description coverage and no usage guidance, an agent has to guess how to specify the repository name and when to prefer this over nexus_explain_storage_strategy.

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% for the single required "name" parameter, so the schema gives no semantics. The description only implies that name identifies the repository being explained; it does not state expected format (bare name vs. full path/qualified name) or error behavior for unknown repositories.

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 gives a specific verb ("Explain") and resource ("one repository") plus the facets covered: storage, groups, cleanup policies. That separates it from siblings like nexus_audit_repository_content or nexus_generate_inventory_json, though it does not distinguish it from the closely related nexus_explain_storage_strategy.

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?

There is no when-to-use guidance, no exclusions, and no pointer to alternatives despite several overlapping siblings (explain_storage_strategy, audit_repository_content, compare_live_state_with_declared_state). The agent must infer that this is the explanatory/read-out tool rather than an audit or generation tool.

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