wealthbox.workflows.list

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

The description only says 'List workflows' and enumerates query parameters, with no mention of the read-only nature, response format, pagination defaults, or any side effects. Since no annotations are provided, the description carries the full burden of behavioral disclosure and fails to address these aspects.

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, using one sentence to state the action and a compact list for parameters. It front-loads the core purpose and wastes no words.

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's nested query object with six optional parameters and no output schema, the description is incomplete. It does not describe the response structure, default pagination behavior, or parameter details. The minimal information provided is insufficient for an agent to know what the tool returns or how to use it effectively.

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 description lists the query parameter names (status, template_id, updated_since, updated_before, page, per_page) but does not provide any additional semantics beyond the schema's property names. It does not explain expected value formats, allowed values, or how parameters interact. With schema description coverage at 0%, the description fails to compensate.

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 'List workflows,' which clearly identifies the action (listing) and the resource (workflows). This distinguishes it from sibling tools like workflows.get, create, and delete, as well as other entity list tools. However, it lacks additional context about what constitutes a workflow or the scope of the list.

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 query parameters that imply filtering and pagination use cases, but it does not explicitly state when to use this tool versus alternatives such as workflows.get or other list tools. No exclusions or alternative recommendations are mentioned, leaving the agent to infer usage from the tool name.

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