Create A New Context

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that it returns the created object on success (HTTP 201) and lists required parameters, but it does not disclose additional behavioral traits such as side effects, permissions, or constraints beyond the schema. It provides some context but not rich detail.

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 contains some redundancy (repeats 'create a new Document Markup records') and includes API endpoint details. It is moderately structured but could be more concise and front-loaded.

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 8 parameters (5 required, 2 enums, nested objects) and no output schema, the description should explain what a context is and how it relates to layers and document markup. It mentions 'organizing layers within a document' but does not fully clarify usage or return structure. Adequate but not fully informative.

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 100% (all 8 parameters have descriptions). The description does not add any meaning beyond the schema; it merely lists required parameters. With high coverage, baseline 3 is appropriate.

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?

Description clearly states the tool creates a new context for organizing layers within a document and mentions it creates Document Markup records. It specifies the success response (HTTP 201) and lists required parameters. However, it could better differentiate from other create tools among the many siblings.

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 says to 'use this to create a new Document Markup records' but provides no guidance on when to use this tool versus alternatives, no exclusions, and no mention of when not to use it. Among thousands of sibling tools, this is a significant gap.

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