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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral trait beyond that — results are returned 'newest first' — but says nothing about how far back the log goes, retention, or pagination behavior beyond what the schema documents.

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 sentences, front-loaded with what the log contains, followed by the endpoint path. Nothing is wasted, though the raw GET path is of limited use to an agent deciding whether to call the tool.

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, paginated list tool with fully documented parameters, the description covers what the resource is and the ordering of returns. The absence of an output schema means the shape of individual log entries is undocumented, but that is a minor gap for this tool class.

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%: page, per_page, server_id and webapp_id all carry their own descriptions, including the cross-reference hints (see runcloud_list_servers / runcloud_list_webapps). The description contributes no parameter meaning beyond the path template, 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 resource (a web application's activity log) and enumerates the event types it contains (settings changes, PHP version changes, deployments), which makes its scope concrete. It does not explicitly contrast itself with the nearest sibling, runcloud_list_server_logs, so an agent must infer the webapp-vs-server distinction from the name alone.

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 explicit when-to-use statement, no prerequisites, and no routing to an alternative log tool. Usage is only implied by the enumerated log contents (e.g. auditing deploy or PHP version changes), which is the minimum viable level.

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