code_workspace_get_run

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

No annotations are present, so the description must disclose behavioral traits. It only says 'Get the details', implying a read operation, but it does not confirm read-only behavior, mention permissions, rate limits, or potential side effects. Minimal disclosure.

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 a single sentence, which is concise. However, it is under-specified and lacks crucial details needed for correct tool invocation. While no fluff is present, the description does not earn its place because it omits important information.

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 tool has two required parameters, an output schema exists, and many sibling tools are present, the description is incomplete. It does not clarify what 'details' entail, does not help differentiate from similar tools, and does not reassure the agent about the parameters needed.

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%, meaning the schema provides no descriptions for the two parameters. The description adds no additional meaning; it does not explain what workspace_id or run_id represent or their expected formats. The parameter titles (Workspace Id, Run Id) are derived from the schema, but no further context is given.

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 'Get the details for a specific coding run' clearly states the verb 'Get' and the resource 'details for a specific coding run'. It succinctly distinguishes this tool from siblings like code_workspace_get_active_run and code_workspace_runs.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., code_workspace_runs for listing runs, code_workspace_get_active_run for the active run).

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