workspace-bySlug

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

With no annotations present, the description should disclose behavioral traits. It only states that it retrieves a workspace, but omits details about authorization needs, error conditions, or any side effects. For a read-only operation, it lacks sufficient behavioral context.

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 short, but the appended '(Tags: Workspaces)' is superfluous and does not aid tool selection. It could be more concise by removing the tag. Overall, it functions but wastes space.

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 the simplicity (1 param, no output schema), the description is inadequate. It does not specify return value structure, possible errors, or any context about workspace uniqueness. An agent would need additional information to use it effectively.

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 does not explain the workspaceSlug parameter beyond its name. It adds no value regarding format, constraints, or purpose beyond what is inferred from the name.

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 'Retrieves a workspace by its slug', specifying the verb, resource, and identifier. It distinguishes from sibling tools like workspace-byId and workspace-all, which retrieve by different criteria.

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 is provided on when to use this tool versus alternatives such as workspace-byId or workspace-all. The agent is not informed about prerequisites or situations where this tool is preferable.

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