List Endpoints

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

With no annotations, the description carries the full burden for behavioral disclosure. It states the tool lists all endpoints with method and path, implying a read-only operation, but does not disclose any additional traits such as pagination, ordering, or whether filters are case-sensitive. The simplicity of the operation makes this acceptable, but more could be said.

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 sentence that immediately conveys the primary purpose and output. There is no redundant text or structural issues; it is highly concise and front-loaded.

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 with two optional parameters and an output schema that documents the return format. The description covers the essential information (what it lists and the output fields). Nothing critical is missing for an agent to call it correctly, though a note on read-only nature or explicit 'returns a list' could add slight completeness.

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 100%, both 'app' and 'method' parameters are fully described in the schema. The description adds no additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 clearly states the verb 'List' and the resource 'available UniFi API endpoints' with the specific output 'HTTP method and path'. This distinguishes it from siblings like search_endpoints (which implies searching) and get_endpoint (which implies a single endpoint retrieval).

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 implies usage by mentioning optional filters, but it does not explicitly state when to use this tool versus alternatives, nor does it provide any exclusions or conditions. The context signals show siblings that might overlap, but the description lacks direct guidance on selection.

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