get_executed_workflows

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

No annotations are provided, so the description carries full burden. It mentions scoping to the current session and pagination (limit/offset), but does not specify ordering (e.g., latest by time) or result behavior beyond filtering. This is adequate but not exhaustive.

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?

Two sentences, no filler. Front-loaded with main purpose and clearly structured by parameter condition. Every sentence adds value.

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 4 optional parameters and no output schema, the description covers the main use cases and parameter behavior. It lacks output format details but is sufficient for a retrieval tool with pagination. Some minor gaps in behavioral specifics.

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?

With 0% schema description coverage, the description must compensate. It explains id and workflow_id filtering, and implies limit/offset for pagination. However, it does not specify data types or ordering details for 'latest results', leaving some ambiguity.

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 it retrieves executed workflows for the current session, and distinguishes three use cases: by id, by workflow_id, or paginated list. This differentiates it from sibling tools like list_workflows which likely list workflow definitions.

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 explains when to use each parameter: id for single record, workflow_id to filter by workflow, and no parameters for paginated latest results per session. It provides clear context for usage, though it does not explicitly state when not to use this tool or compare to siblings.

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