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 states it 'fetches' details, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior beyond the basic action.

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 extremely concise and front-loaded, consisting of a single sentence that directly states the tool's purpose. Every word earns its place, with no redundant information or unnecessary elaboration, making it efficient and easy to parse.

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?

Given the complexity (a read operation with one parameter) and lack of annotations and output schema, the description is incomplete. It doesn't explain what 'full execution details' include, the return format, error handling, or authentication needs. For a tool in a workflow management context with siblings like 'get_execution_trace', more context is needed to understand its role and output fully.

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?

The description adds minimal meaning beyond the input schema. It mentions 'execution ID' as the parameter, which aligns with the schema's single 'executionId' property. However, with 0% schema description coverage, the schema provides no details about the parameter's format or constraints. The description doesn't compensate by explaining what an execution ID is, its format, or where to obtain it, leaving the parameter semantics largely undocumented.

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 the verb ('Fetch') and resource ('full execution details'), specifying it's done 'by execution ID'. It distinguishes from siblings like 'list_executions' (which lists multiple) and 'get_execution_trace' (which likely provides trace-specific details). However, it doesn't explicitly contrast with 'get_workflow_summary' or 'evaluate_workflow_result', which might also retrieve execution-related data, leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid execution ID), exclusions (e.g., not for listing executions), or compare to siblings like 'list_executions' for multiple items or 'get_execution_trace' for trace-specific data. The description implies usage by stating 'by execution ID', but this is minimal and lacks explicit context.

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