list_workflow_steps

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

No annotations provided, so description carries full burden. States it lists steps and returns a list, but does not disclose read-only nature or other behavioral traits. Since it's a simple list operation, the lack of extra detail is acceptable but not exemplary.

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?

Description is front-loaded with the main purpose, includes structured Args/Returns/Examples sections, and every sentence adds value. No waste.

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?

Tool has one optional parameter and an output schema (not shown but indicated). The description explains the parameter and return type adequately given the presence of output schema. Complete for this simple 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 0%, meaning description adds value. The description explains 'project: Project name (uses default if not specified)' which clarifies the parameter's purpose and default behavior beyond the schema's type and default values.

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?

Clearly states 'List all steps in the workflow' and 'Provides an overview of all numbered steps in the project's workflow.' Distinct from siblings like get_next_step (singular step) and get_workflow_section (section focus).

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?

Provides parameter details and examples, showing usage with and without project argument. Does not explicitly contrast with sibling tools but the purpose is clear enough that an agent can infer when to use it based on need.

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