herdr_workspace_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' indicates a read operation, but the description does not disclose response format, error or not-found behavior, permissions, or side effects. This leaves the tool's behavior largely to inference.

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 one short, front-loaded sentence with no filler. For a one-parameter getter, this is an appropriately concise size and structure.

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 and no annotations, the description leaves the return shape and selection criteria unspecified. It also does not clarify how to obtain the workspace ID or how this differs from workspace_list. The tool is simple, but the description remains too minimal for an agent to invoke it with full confidence.

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% and the description adds no meaning to workspace_id beyond its self-explanatory name. It does not specify that workspace_id is the unique identifier of the workspace or describe how to obtain it. With only one parameter, the gap is modest, but the description still fails to compensate for the missing schema documentation.

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 uses a specific verb ('Get') and a clear resource ('a workspace'), so an agent can tell this is a singleton lookup rather than a list operation. It differentiates from the sibling herdr_workspace_list, though it does not explicitly name it. 'Details' is somewhat generic, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus workspace_list or other getter tools such as agent_get or pane_get. The only usage cue is the workspace_id parameter in the schema, but the description never mentions it. No when-not conditions or alternative routing are provided.

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