nexus_openapi_list_operations

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only the useful nuance that the document is 'live' (fetched from the running instance) rather than static, but says nothing about result size, pagination, or failure behavior when the instance is unreachable.

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 redundant wording; the discriminating detail ('live') is placed where it will be read. It is arguably too terse, since one more clause about what is returned or when to prefer it would earn its space.

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 an output schema present and rich annotations, the description does not need to explain return values or safety. However, for a discovery tool sitting among eleven repository-analysis siblings, it should say how it relates to them (e.g., use this to enumerate endpoints before calling compare_live_state_with_declared_state), which it omits.

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 takes zero parameters and the input schema has no properties, so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies.

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 ('List REST operations') plus a qualifier about the source ('from the instance's live OpenAPI document'), which separates it from the repository-analysis siblings. It stops short of naming a sibling it complements or replaces, so an agent must infer the boundary itself.

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 explicit when-to-use or when-not-to-use guidance. The word 'live' hints that this is for runtime discovery rather than declared-state inspection (as in nexus_compare_live_state_with_declared_state), but the description never states that distinction or any prerequisite such as the instance being reachable.

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