herdr_pane_list

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

With no annotations, the description carries the burden but only states a 'List' operation and an optional filter. It does not explicitly note read-only behavior, whether the list is scoped to the caller, or whether any state changes occur. This is minimal but not misleading.

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?

One short sentence communicates the operation and the only option. Every word is useful, and it is front-loaded and direct.

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 1-parameter list tool the core behavior is stated, but there is no mention of the return shape and no distinction from the similarly named herdr_owned_pane_list. Without an output schema or annotations, that leaves an agent to guess what 'panes' resolves to and which list variant is appropriate.

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 already documents the single 'workspace' parameter as a filter (100% coverage). The description's 'optionally filtered' adds no new semantic detail beyond 'optional'; 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?

States a clear verb ('List') and resource ('panes') plus the optional workspace filter. However, it doesn't differentiate from the sibling herdr_owned_pane_list, so the agent cannot tell the difference between the two list tools from this description alone.

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 no explicit when-to-use guidance compared to sibling tools such as herdr_owned_pane_list, herdr_pane_get, or herdr_pane_read. The only usage signal is the optional workspace filter, which is parameter-level rather than tool-selection guidance.

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