Create stage

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds an auth requirement (ADMIN/OWNER role), which is a useful behavioral trait beyond the annotations. No contradiction exists.

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 action, and includes the essential role requirement. Every word is purposeful with no redundancy.

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 full schema and annotations, the description is adequately complete for a straightforward create tool. It could differentiate from the many sibling stage tools, but the role requirement and clear purpose make it sufficient for an AI agent to select it correctly.

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 all five parameters are already documented. The description adds no additional parameter semantics, but the schema carries the burden effectively, meriting the baseline score of 3.

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 states 'Create a stage on a board' with a clear verb and resource. The verb 'create' distinguishes it from sibling tools like update_board_stage, delete_board_stage, reorder_board_stages, and start_board_stage, making the purpose unmistakable.

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 the role requirement (ADMIN/OWNER) as a prerequisite, but it does not explicitly state when to use this tool versus alternatives such as update_board_stage or reorder_board_stages. Usage is implied by the name and title rather than explicitly guided.

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