get_workflow

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

No annotations provided. Description implies read-only behavior by stating 'Read and parse', but does not detail side effects, error handling, or permissions. Adequate for a simple read tool but minimal.

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?

Extremely concise: two sentences. The Args line is redundant with schema but not harmful. No fluff, though could briefly mention that it's a safe read operation.

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 simple single-param tool and existence of output schema, description covers main action. Lacks mention of error conditions (e.g., invalid YAML, file not found), but return values are in output schema. Good enough for a basic 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 description coverage is 0%. The description adds only 'Path to the YAML workflow file' for the parameter, which restates the type and name. Does not specify format, relative vs absolute, or constraints.

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?

Description uses specific verb 'Read and parse' and resource 'workflow YAML file' with clear outcome 'returning its full structure'. Clearly distinguishes from siblings that create, validate, run, or list workflows.

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 on when to use vs alternatives like list_workflows or validate_workflow. No mention of prerequisites (e.g., file must exist) or when not to use.

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