openwisp_get_cert

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

No annotations are provided, so the description carries the burden. It does disclose the HTTP GET method and endpoint path, which implies a safe, non-mutating lookup, but it says nothing about authentication/permission requirements, error behavior for unknown IDs, or response characteristics. This is minimal but not absent disclosure.

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?

Two short fragments, front-loaded with the action and resource, with the endpoint as trailing parenthetical detail. Nothing is wasted and the key information comes first.

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 one-parameter read operation this is close to sufficient, but with no output schema the description should ideally hint at what "details" actually contains. As written, an agent knows how to call it but not what it will get back.

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?

With a single parameter and 100% schema description coverage, the schema already documents "id" as a "Certificate UUID or ID". The description adds nothing beyond that, so the baseline 3 applies.

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 specific verb and resource ("Get certificate details") and places it in the Certificates & VPN category, so it is distinguishable from siblings like openwisp_list_certs, openwisp_create_cert, and openwisp_revoke_cert. However, it never explicitly contrasts itself with those siblings, and "details" remains somewhat vague about what is retrieved.

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 stated when-to-use context, no prerequisite (e.g., needing an existing certificate ID), and no mention of alternatives such as openwisp_list_certs for enumeration or openwisp_get_ca for the issuing CA. The agent must infer usage entirely from the name.

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