herdr_tab_list

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

With no annotations, the description carries the full burden of disclosure. It implies a read-only operation via 'List', but it does not state whether there are side effects, authentication requirements, pagination, or ordering. For a simple list tool this is acceptable, but additional context like return format or default scope would improve transparency.

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?

A single, front-loaded sentence that conveys the core action and the optional filter. There is no wasted language, and the description is appropriately brief for a simple tool.

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?

The tool is low complexity (one optional parameter, no nested objects, no output schema). The description covers the essential purpose and the parameter's role. While it does not describe the output format, the list action is straightforward, and naming conventions align with sibling tools. It is nearly complete for an agent to call it correctly.

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 only defines a 'workspace' string with no description, and schema coverage is 0%. The description compensates by explicitly stating 'optionally filtered to a workspace', clarifying the parameter's purpose. This adds meaning beyond the schema, so the score is above baseline.

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 lists tabs and optionally filters by workspace. It distinguishes from herdr_tab_get (which presumably gets a single tab) and other list tools by naming the resource and the optional filter. It could explicitly name sibling alternatives, but the purpose is unambiguous.

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 this is the tool for listing tabs, but it provides no explicit guidance on when to use it versus alternatives like herdr_tab_get or other list tools. There is no mention of conditions, exclusions, or prerequisites. The usage context is left to inference.

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