plane-state-create

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

No annotations present. Description only says 'Create' without disclosing side effects (e.g., changing workflow behavior), permissions needed, or constraints like maximum states per group. Insufficient behavioral disclosure for a mutation tool.

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?

Single sentence, no extra words. Minimal structure but not overly verbose. Could benefit from additional context without being wasteful.

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?

Lacks information on return value (likely the created state object), error conditions, or constraints like unique state names per project. Given no output schema, description should compensate but fails.

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?

All 4 parameters are fully described in the input schema (100% coverage), so schema carries the semantic weight. The description adds no additional parameter context beyond the schema, thus baseline 3 is not justified; score 2 because no value added.

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 'Create a new workflow state in a project.' Verb 'Create' and resource 'workflow state' are specific and differentiate from sibling list tool plane-state-list. However, it could better emphasize it's adding a state to a specific project.

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 on when to use this tool versus others. Does not mention prerequisites like project existence or relationship to state groups. Missing context on usage scenarios.

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