marrow_list_templates

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

With no annotations, the description carries the full burden. It indicates a read-only browse/filter operation through the words 'Browse' and 'Filter,' but it does not explicitly state non-destructiveness, auth requirements, pagination behavior, or return format. It adds context about discovering templates before installing, which is useful but not comprehensive.

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?

Two sentences, front-loaded with the main purpose, followed by filtering details and the intended use case. Every word earns its place with no redundancy or filler.

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?

For a simple list tool with three optional, well-documented parameters, the description is largely complete. It explains what the tool does, how to filter, and when to use it. However, it does not describe the return value structure or whether pagination beyond the limit parameter exists, which is a minor gap given the lack of an output schema.

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?

All three parameters are fully documented in the schema (100% coverage), so the description adds little beyond what the schema provides. The mention of industry examples mirrors the schema's own examples. The description does not introduce new semantics or clarify edge cases, so a baseline 3 is appropriate.

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 tool's function: 'Browse pre-built workflow templates' and distinguishes it from siblings like marrow_install_template by adding 'Use to discover available workflows before installing.' This makes the purpose obvious and specific.

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 clear context for when to use the tool ('Use to discover available workflows before installing'), implying a pre-installation discovery role. It does not explicitly name alternative tools or list exclusions, but the 'before installing' phrase strongly suggests the relationship with install_template.

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