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 the underlying endpoint (GET /servers/{id}/webapps/{webapp}) and the returned field list, which is modest additional context, but says nothing about failure modes when the id is unknown or whether the record is fetched live.

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 compact sentences, front-loaded with the object and its return fields. The trailing raw endpoint restates the same idea in a second notation and is close to redundant, but the overall length is tight and nothing is buried.

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?

With no output schema, the description's field enumeration (path, PHP version, stack, type, default flag) is a valuable substitute that tells the agent what it will receive. It is close to complete for a simple read-by-id tool, though it omits any note about unknown/invalid id behavior.

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 coverage is 100%: both server_id and webapp_id are documented with descriptions pointing at runcloud_list_servers and runcloud_list_webapps respectively. The description adds no parameter-level meaning beyond what the schema provides, 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: fetches one web application by id, and enumerates the fields returned (path, PHP version, stack, type, default flag). This distinguishes it from runcloud_list_webapps, but it never names that sibling or the related runcloud_get_webapp_settings/runcloud_get_webapp_ssl, so the differentiation is implicit rather than explicit.

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 guidance and no alternatives named in the description. An agent must infer from the tool name alone that this returns a single webapp versus runcloud_list_webapps (all webapps) or runcloud_get_webapp_settings/runcloud_get_webapp_ssl (adjacent data for the same object).

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