createMock

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

The description adds context beyond annotations by explaining the UID resolution process and workspace requirement. It discloses behavioral traits like requiring collection UID and workspace scoping. 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 bullet points, front-loads the primary purpose, and every sentence adds value. No unnecessary 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 no output schema, the description does not explain return values, but it covers critical parameter constraints (UID resolution) and workspace usage. It is sufficient for a creation tool, though error conditions or permissions are not mentioned.

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 description adds critical meaning beyond the schema: it clarifies that collection must be a UID (ownerId-collectionId), not a bare ID, and provides detailed resolution steps. This is a significant addition over the schema's limited description.

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 'Creates a mock server in a collection' using a specific verb and resource, and distinguishes from sibling tools like createCollection or createEnvironment by specifying the mock server context.

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 provides explicit instructions on using the collection UID instead of bare ID, steps to resolve UID, and workspace scoping. It implies when to use this tool (to create a mock server) but does not explicitly contrast with alternatives like updateMock or publishMock.

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