herdr_tab_create

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

Annotations already declare the full safety profile (not read-only, non-idempotent, non-destructive, closed-world), so the description is not the sole carrier of behavior. It adds only the implicit fact that workspace targeting is optional, and says nothing about defaults, auth, or side effects — acceptable but thin with annotations present.

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 short sentence with the core action front-loaded and the optional scoping tacked on. Zero wasted 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?

For a simple create tool with a fully documented schema and annotations covering safety, the description covers purpose and scoping adequately. The only real gap is not stating the default workspace behavior when workspace_id is omitted.

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 100%, so all four parameters (cwd, focus, label, workspace_id) are already documented in the schema. The description only restates workspace_id as optional, adding no syntax or format meaning beyond the structured fields.

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?

Specific verb (Create) + resource (a tab) with a stated scope modifier (optionally in a specific workspace). It is clearly distinguishable from herdr_tab_close and herdr_tabs by the create verb, but it never names or contrasts those siblings.

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 on when to use this versus alternatives such as herdr_open_agent or herdr_workspace_create, no prerequisites, and no statement about what happens when workspace_id is omitted. The agent must infer all usage context.

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