openwisp_list_certs

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

No annotations are provided, so the description carries the full burden; it does disclose the HTTP method and endpoint (GET /api/v1/controller/cert/), which signals a safe, non-mutating read. It says nothing about auth requirements, pagination, or result size limits, which are the main behavioral unknowns for a list endpoint.

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?

One compact sentence with the category tag front-loaded and the purpose immediately readable. It is efficient, though the category prefix and endpoint restatement add little beyond the name itself.

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 read tool with no output schema and no annotations, this is barely enough: the agent knows what it lists but not what comes back, whether results are paginated, or what permissions are needed. Adequate minimum-viable coverage, not complete.

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, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter meaning is degraded or contradicted.

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+resource ('List certificates') and even names the backing endpoint, so the agent knows it is a read of the certificate collection rather than a single cert. It does not, however, differentiate itself from the many sibling cert tools (openwisp_get_cert, openwisp_renew_cert, openwisp_list_cas) beyond the singular/plural distinction.

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 when-to-use or when-not-to-use guidance and no named alternatives; the agent must infer from the word 'List' that this is the browse/all-certificates entry point. With siblings like openwisp_get_cert and openwisp_list_cas present, an explicit routing hint would have been cheap and valuable.

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