Create a subitem

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

Annotations already mark readOnlyHint=false and destructiveHint=false, covering the mutation safety profile. The description adds valuable behavior: 'Column values apply in a second step, because a subitem lives on its own hidden board.' This explains a non-obvious trait that column values are not set immediately, going beyond the annotations. No contradiction.

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 two sentences long, front-loaded with the core action and followed by a concise behavioral note. Every word earns its place, with no redundant details or repetition of schema fields.

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 moderate complexity, the description covers the main purpose, the crucial caveat about column values, and the hidden-board rationale. It lacks explicit return value details, but there is no output schema, and for a create operation this is often implied. The descriptions and annotations together provide sufficient context.

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%, so baseline is 3. The description adds meaning to the 'values' parameter by explaining why column values are not applied immediately, which helps the agent understand the parameter's optionality and timing. It does not reformat the schema but enriches the semantic context.

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's purpose: 'Creates a subitem under a parent item.' This uses a specific verb and resource, distinguishing it from the sibling 'monday_create_item' which creates top-level items. The additional note about column values applying later further clarifies its specific role.

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 implies usage context by explaining that column values are not applied immediately due to the subitem's hidden board. This clues the agent that a second step is needed, but it does not explicitly name alternatives or when to choose this over 'monday_create_item'. Clear context with no exclusions, hence a 4.

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