morpheus_list_models

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

With no annotations provided, the description carries the behavioral disclosure burden. It indicates an HTTP GET, which implies a read-only operation with no side effects, and the list use case suggests non-destructive behavior. However, it does not explicitly state the read-only nature, nor does it address auth, rate limits, or other behavioral traits that could affect an agent's invocation.

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?

Single sentence with no filler; it states the operation, the endpoint, and two concrete use cases. The parenthetical adds useful context without bloating the description.

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?

Given the tool has no parameters, an output schema exists to define return values, and the implementation is a simple list operation, the description is complete. It gives the endpoint and use cases, so an agent can invoke it correctly. It does not need to explain return structure since the output schema is available.

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 schema confirms an empty object, so the baseline for parameter semantics is 4. The description adds no parameter-level detail, but none is needed since there are no parameters to document.

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 uses a specific verb ('List') and resource ('models') and names the exact endpoint GET {base}/models. It clearly distinguishes this from the sibling tools morpheus_chat and morpheus_embed, which serve different purposes.

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 parenthetical '(install smoke + model picker)' gives concrete contexts where this tool should be used. It does not explicitly mention alternatives or when not to use it, but with only chat and embed as siblings, the usage boundary is clear enough.

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