wealthbox.workflowTemplates.list

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

There are no annotations, so the description must carry the burden. It mentions 'Query params: page, per_page', indicating pagination behavior, which is useful. However, it does not disclose the response format, default per_page value, or explicitly confirm read-only semantics, relying on the verb 'List' to imply safety.

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 two short sentences with no filler. The main purpose is front-loaded, and the query parameters are listed succinctly, making it easy to parse quickly.

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 there is no output schema, the description should describe what the response contains (e.g., a list of workflow template objects) and any pagination details. It only mentions the input parameters, leaving the agent without expectations for the output or behavior like default limits.

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%, so the description must compensate. It names 'page' and 'per_page' as query parameters, adding context that they are query string parameters rather than body fields. However, it does not explain their meaning or constraints (e.g., defaults, maximums), leaving room for ambiguity.

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 workflow templates' with a clear verb and resource, effectively distinguishing it from sibling tools like wealthbox.workflowTemplates.get (retrieve a single template) and wealthbox.workflows.list (list workflows, not templates).

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 is provided on when to use this tool versus alternatives, such as when to use list vs get, or any edge cases like pagination defaults. The tool name alone implies the use case, but the description does not explicitly state it.

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