da_list_endpoints

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

With no annotations, the description carries the behavioral burden. 'List' and 'from official swagger' reasonably indicate a read-only introspection operation with no side effects, but the description does not explicitly confirm read-only behavior, auth requirements, or pagination/response shape beyond what the output schema likely provides.

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 compact and front-loaded: one clear purpose sentence followed by a terse parameter breakdown. Every sentence contributes useful information, with no repetition or filler.

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 simple endpoint-listing tool with only two optional parameters and an output schema, this is nearly complete. It lacks only explicit guidance about when to choose a sibling discovery tool, but an agent can invoke it correctly based on the provided description and schema.

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 Args section adds meaningful detail beyond the bare schema: prefix is explained as a path prefix filter with concrete examples, and method is labeled as an optional HTTP method filter. This compensates well for the 0% schema description coverage.

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 a clear resource ('New API operations bundled with this server'), sourced from the official swagger. It is distinguishable from a tool like da_describe_endpoint, which would describe a single operation, though it does not explicitly name that sibling.

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 intended use is implied: call this to discover available API operations from the server's swagger definitions. However, there is no explicit guidance about when to prefer this over related discovery tools such as da_describe_endpoint or search_resources, and no exclusions are stated.

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