List hosted sites & apps

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

The description declares it read-only, which is a key behavioral trait. However, without annotations, it could detail authorization needs or response format. The offered detail is good but not exhaustive.

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?

Single, well-structured sentence front-loads the read-only nature and lists components precisely. No unnecessary words.

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 description covers the tool's domain and scope adequately, given no output schema. Could mention response structure or limits, but sufficient for understanding.

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 description does not add meaning beyond the input schema; the parameter 'host' is fully described in the schema. Baseline 3 applies due to high schema 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 clearly states it lists hosted sites and apps, specifying nginx sites, PM2 processes, and systemd services. It distinguishes from sibling tools like list_hosts and server_health by focusing on inventory.

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 for inspecting server hosting, but does not explicitly state when to avoid using it or contrast with alternatives. Context from sibling tools suggests differentiation, but lacking explicit guidance.

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