get_workflow

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the tool is read-only (likely), if it requires authentication, or what happens if the workflow doesn't exist. It doesn't explain the output behavior beyond 'snapshot', leaving agents with no insight into side effects or access requirements.

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 very short (4 words) and front-loaded, but it lacks substance. While concise, it does not earn its place because it provides minimal information. It could be expanded with key details without losing conciseness.

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 tool has an output schema (unseen) but no parameter descriptions and zero schema coverage, the description is incomplete. It doesn't explain the return format, how to interpret the snapshot, or what scenarios require this tool. With siblings like 'get_workflow_events' and 'list_workflows', more context is needed for proper selection.

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 input schema has one parameter 'params' with a generic object type (additionalProperties: true) and no description. Schema description coverage is 0%, so the description must compensate, but it adds nothing about the parameter's meaning, structure, or required fields. The description fails to clarify how to identify the workflow (e.g., by ID).

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 states the tool retrieves a workflow snapshot, which is moderately clear. However, it doesn't specify what 'snapshot' means exactly (e.g., status, metadata, full definition). The verb 'Get' is standard for retrieval, but the resource 'workflow snapshot' could be more precise. Compared to sibling tools like 'get_workflow_events', it's distinct but not fully differentiated.

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 siblings like 'get_workflow_events' or 'list_workflows'. It doesn't mention prerequisites (e.g., workflow ID needed) or context. There's no when-not-to-use or alternative suggestions.

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