get_execution

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds real value beyond them by describing the payload shape ('comprehensive JSON with per-stage results') and the scope of data returned. It does not mention pagination or size limits, but for an ID-scoped read those are minor.

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?

Three sentences, all load-bearing: what it returns, why to call it, and where the ID comes from. The purpose is front-loaded and nothing is repeated from the name or annotations.

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 single-parameter read tool with no output schema, the description adequately compensates by summarizing the return contents and the sourcing of the ID. A note on result size or error behavior (e.g. not-found handling) would make it fully self-sufficient.

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%, so the baseline is 3; the description still earns extra by naming three provenance sources for execution_id (trigger_pipeline, list_executions, search_executions), one more than the schema itself lists. It adds no format details beyond the schema's UUID note.

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 ('Get the full details of a single pipeline execution by its ID') and enumerates the returned content (stage statuses, outputs, variables, timing). This clearly distinguishes it from sibling list_executions/search_executions, which return many executions rather than one.

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 concrete use cases ('debug a failed deployment or inspect execution progress') and tells the agent where the required ID comes from (trigger_pipeline, list_executions, search_executions). It stops short of an explicit when-not rule, but the single-vs-list split is implied well enough to route correctly.

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