netbox_list_endpoints

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

With no annotations, the description carries the behavioral burden. It makes the non-mutating, discovery-oriented behavior clear by stating that the tool lists supported endpoint values and provides explanatory descriptions. It does not discuss rate limits, auth requirements, or response size, but for a read-only catalog tool this is not a major gap.

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 a single well-structured sentence that front-loads the core function, then adds the grouping detail and the critical usage instruction. Every phrase earns its place with no redundant or filler content.

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 discovery tool with an output schema, the description is complete: it explains what is returned, how it is organized, and why/when to invoke it. The presence of an output schema covers the return-value shape, and the sibling tool names give enough context for the agent to see where this tool fits.

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, so there are no parameter semantics to document. The description usefully reinforces that the tool takes no arguments and simply returns the endpoint catalog. Per the baseline for zero-parameter tools, this is appropriately handled.

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 states a clear, specific action ('List every supported NetBox app.endpoint value') and explains the output structure (grouped by app, with descriptions). This clearly distinguishes it from sibling tools like netbox_list_objects, which list object records rather than endpoint metadata.

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 explicitly tells the agent to call this tool first and explains why: to discover valid endpoint strings for the other tools. It provides clear usage context but does not explicitly name alternative tools or state when not to use it.

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