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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint path and the list of setting categories, without noting auth requirements, rate limits, or return format beyond the category hints.

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?

A single tight sentence front-loads the resource and enumerates the key setting categories, followed by the endpoint. No filler text; the trailing endpoint is arguably redundant given annotations already carry the title.

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 read-only getter with annotations covering safety and a fully documented schema, the description is nearly complete. With no output schema, the enumeration of returned setting categories (disabled functions, timezone, limits, process manager) usefully anticipates the payload, though it stops short of describing structure or pagination.

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% and both parameters (server_id, webapp_id) are documented in-schema with cross-references to runcloud_list_servers and runcloud_list_webapps. The description adds no parameter-level detail, 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?

States a specific verb+resource (get settings of a web application) and enumerates the concrete setting categories returned (disabled functions, timezone, memory/upload limits, process manager), which distinguishes it from a plain get_webapp. It doesn't explicitly contrast with siblings like runcloud_get_webapp_ssl, but the scope is unambiguous.

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?

Usage is only implied: an agent can infer you call this when you need PHP/FPM/Nginx configuration for a webapp, but there is no statement of when to prefer it over runcloud_get_webapp or runcloud_get_webapp_ssl, and no prerequisites or exclusions are given.

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