Get Execution

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals one useful behavioral trait: input/output data is excluded unless include_data=True. However, it does not state whether this is a read-only operation, how it handles missing IDs, or what happens if include_data is requested for an execution with no data.

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?

The description is two concise sentences: the first states the primary action and target, the second explains the optional flag. There is no filler or redundant phrasing.

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 simple get-by-ID tool with two parameters and an output schema, the description covers the main actions and the optional data-inclusion behavior. It is adequate for a first-time caller, though it could be more complete by noting that get_execution is a read-only lookup, distinct from execution-triggering siblings.

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 0%, so the description must compensate. It explains execution_id as the identifier of the execution and clarifies that include_data=True controls inclusion of input/output data. This adds meaning beyond the raw schema, though execution_id's semantics are largely inferable from the parameter name.

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?

The description clearly states a specific verb ('Get') and resource ('details of a specific execution by ID'), which is enough to understand the tool's core function. It does not explicitly name sibling alternatives like list_executions, so it stops short of full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus list_executions, execute_workflow, or get_workflow. The only usage-related hint is the include_data flag, which explains an option rather than when the tool should be chosen.

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