create_master_spread

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

Without annotations, the description must disclose behavioral traits, but it only states 'Create a new master spread'. It fails to mention that this is a write operation, potential side effects, required permissions, or default values. The agent is left uninformed about the tool's impact.

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 very concise (one short sentence), which is positive for brevity, but it lacks necessary details, making it insufficiently informative. Every sentence should earn its place; here, the single sentence provides minimal value.

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 5 parameters and no output schema or annotations, the description is incomplete. It does not explain what a master spread is, how creation affects the document, or how to interpret the required parameter relationships. The schema provides some context, but the description should offer more.

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 input schema has 100% description coverage, so the baseline is 3. The description adds no extra meaning beyond the schema; it does not clarify relationships between parameters like name, baseName, and namePrefix. The schema descriptions are adequate but the description provides no additional value.

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 'Create a new master spread', specifying the verb (create) and resource (master spread). This distinguishes it from sibling tools like 'duplicate_master_spread' and 'delete_master_spread', though it lacks additional context about what a master spread is.

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 guidance is provided on when to use this tool versus alternatives such as 'duplicate_master_spread' or 'apply_master_spread'. The description does not include context, prerequisites, or conditions for use.

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