Export Context

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

Annotations provide readOnlyHint and openWorldHint, and the description adds valuable behavioral details: how product context is determined for each format (derived from intent for cursorrules/intent-md, selectable for claude-md). No contradiction with annotations.

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 concise with three focused sentences, each serving a clear purpose: stating overall function, listing formats, and explaining behavioral nuances. No extraneous words.

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's simplicity (3 parameters, no output schema), the description covers the necessary contextual information: format options, parameter usage, and product selection logic. Annotations adequately cover safety and open-world aspects.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining when each format is appropriate, the optional nature of intentId and productId, and the default behavior for product selection in claude-md.

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 the tool exports workspace context as a formatted file, listing three specific formats (claude-md, cursorrules, intent-md) with distinct uses. It differentiates well from sibling tools, none of which provide this export functionality.

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?

The description explicitly tells when to use each format and provides context: for claude-md pass productId to select a product, otherwise the first active product is used; for cursorrules/intent-md product context is derived from the resolved intent. This guides the agent effectively.

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