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

With readOnlyHint=true already covering the safety profile, the description still adds real behavior: the default cluster-vs-organisation scoping rule and what the result set contains (status, error_excerpt, step_summary counts, timestamps). It does not contradict the annotation. It omits any note on ordering/recency window or truncation beyond the limit parameter.

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?

Front-loaded with purpose and default scope, then return fields, then use case, then filter mechanism. No sentence is filler; the two short parenthetical clarifications earn their place.

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 usefully enumerates the returned fields and explains the internal-execution default, which is the main ambiguity for this tool. The remaining gap is the required/optional status of cluster_id, which conflicts with the schema's 'required' list.

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%, so the baseline is 3. The description adds a little scoping context but also introduces an inconsistency: it says 'pass cluster_id or cluster_name to narrow' even though the schema has no cluster_name and marks cluster_id as required, which could mislead an agent about optionality.

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 and resource ('List recent platform executions') and defines the resource concretely as 'deployments, write operations', which separates it from the many get_*/list_* siblings (get_execution_details, list_agent_runs, list_data_runs). It also states the scope rule: current cluster by default, whole organisation when no cluster context exists.

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?

Gives an explicit use case ('investigate what changed recently or which deployments failed') and a filtering hint ('Filter by status ... for focused queries'). It does not name alternatives such as get_execution_trends or get_execution_details for drill-down, so it stops short of full when/when-not routing.

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