dns_list_apps

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List') and the result ('current status') but does not mention that this is a read-only operation, whether any permissions are needed, or what side effects (if any) might occur. This is a minimal description with no extra behavioral context.

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, concise sentence that is front-loaded with the verb and resource, then adds the status detail. Every word contributes meaning, with no wasted or redundant phrasing.

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?

Given that there are no parameters and no output schema, the description provides a reasonable summary of the return value: installed apps and their status. However, it does not specify what constitutes 'status' (e.g., running, stopped, error) or the format of the returned list, so it is not fully complete, but adequate for a simple list operation.

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, and the schema is empty. The baseline for no parameters is 4, and the description adds no parameter details (none are needed). It does not attempt to describe parameters that don't exist, so it fully satisfies this dimension.

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 resource ('installed DNS apps') plus the added detail of 'current status'. This clearly distinguishes it from siblings like dns_list_app_store (which lists available apps in the store) and dns_get_app_config (which retrieves a specific app's config).

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 context of 'installed' implies this is for checking what is already on the server, as opposed to dns_list_app_store for available apps. However, the description does not explicitly state when to use this tool vs. alternatives or provide any exclusion criteria, leaving the guidance merely implied.

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