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

The annotations already indicate read-only and non-destructive behavior, and the description does not add further behavioral details such as pagination, filtering behavior, or side effects. The description is consistent with the annotations, but it provides no extra transparency beyond what is already declared.

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 extremely concise and to the point, consisting of a single sentence. It communicates the essential purpose and return fields without unnecessary verbosity, which is ideal for quick comprehension.

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 that the schema lacks parameter descriptions, the overall description is sparse. It does not convey return format, error conditions, or how to combine parameters (e.g., whether query and folder_id are mutually exclusive). This leaves important context missing for an agent deciding how to invoke the 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?

The schema provides no descriptions for any of the three parameters (limit, query, folder_id). The description only mentions the return fields and does not explain the meaning or usage of these parameters, leaving the agent without guidance on how to set them effectively.

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 the action ('List') and the resource ('the user's workflows'). It also specifies the returned fields (id, name, description, timestamps), making the tool's purpose unambiguous and distinguishing it from siblings like get_workflow which fetches a single workflow.

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 implies usage for listing multiple workflows but does not explicitly contrast with alternatives such as get_workflow or list_workspaces. While the purpose is clear, there is no guidance on when to prefer this over other listing tools, leaving the agent to infer context from the sibling names.

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