get_workspace_status

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

With no annotations, the description must carry the behavioral burden. It implies a read-only inspection operation through 'check' and 'inspect', but it does not explicitly state that it does not modify state, nor does it explain what counts are returned or how the result is structured. Some transparency, but not complete.

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, tightly worded sentence that front-loads the core purpose and adds the deletion context. No filler or repetition; every clause earns its place.

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 has no annotations and no output schema, so the description alone must provide enough context. It covers the high-level purpose but omits the meaning of 'blocking counts', the response shape, the role of the profile parameter, and behavior when the workspace does not exist or cannot be found.

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 compensate for the two parameters. 'workspace' hints at workspace_name, but 'profile' is entirely unexplained, and there is no guidance about required versus optional usage or expected value formats.

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 names a specific verb ('check') and resource ('workspace'), and narrows the purpose precisely: determining whether deletion is possible and viewing blocking counts. This clearly distinguishes it from delete_workspace and list_workspaces.

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?

It explicitly frames the tool as a pre-deletion check ('before deletion'), giving clear context for when it should be used. It does not mention exclusions or name an alternative, but the usage context is strong enough to route an agent correctly.

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