tracecat_get_execution

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

No annotations are provided, so the description carries the full burden. It only states 'Get details' without disclosing read-only nature, permissions required, error behavior, or what exactly constitutes 'details'. This is insufficient for a get operation with no output schema.

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 a single sentence of 8 words with no redundancy. It is appropriately sized but could be slightly more structured to include output hints. However, it is concise and front-loaded with the key action.

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 lack of output schema, the description should explain what 'details' are returned (e.g., status, inputs, outputs, timestamps). It does not, leaving the agent uncertain about the response structure. Error scenarios are also missing. This is incomplete for a read tool.

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% with one parameter 'execution_id' described as 'Execution ID'. The tool description does not add any additional meaning or constraints beyond the schema. Baseline 3 is appropriate as the schema does the work, but no extra value is provided.

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 'Get details of a specific workflow execution' clearly specifies the verb 'Get' and the resource 'details of a specific workflow execution'. It distinguishes from siblings like 'tracecat_get_execution_compact' and 'tracecat_list_executions', which target different granularity or collections.

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 vs. alternatives such as 'tracecat_get_execution_compact' for compact details or 'tracecat_list_executions' for listing. There are no prerequisites or context about which tool is appropriate for different needs.

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