get_workspace_context

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

Although no annotations, the description covers caching behavior, auto-discovery, and env var override. Does not mention side effects or permissions, but reads are typically safe.

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?

Three paragraphs with clear front-loading of purpose. The 'IMPORTANT' line emphasizes usage. Slightly verbose but well-structured.

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 existence of an output schema (not shown), the description adequately explains source, caching, and override without needing return value details. Complete for a read-context tool.

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?

The sole parameter 'reload' is fully described in the schema (100% coverage), and the description adds context about caching and when to use the parameter.

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 starts with 'Get domain-specific context for building RunWhen tasks' and specifies reading a RUNWHEN.md file. This clearly distinguishes it from sibling tools like get_workspace_secrets or get_workspace_config_index.

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?

Explicitly states 'Call this BEFORE writing any task or script to understand the target environment's rules and relationships.' No exclusion of alternatives, but the unique purpose makes the guideline sufficient.

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