zentao_create_story

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

No annotations provided, and the description is extremely brief. It fails to disclose any behavioral traits such as idempotency, required permissions, side effects (e.g., story creation triggers), or return behavior. A mutation tool with no annotation coverage requires rich description, which is absent.

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?

Extremely short (5 Chinese characters) but under-specified. Conciseness should not sacrifice necessary information; this is a case of under-specification rather than efficient communication.

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 complexity (10 parameters, 4 required, no output schema, no annotations), the description is wholly inadequate. It fails to explain what the tool does, when to use it, or what the output looks like. The description provides no value beyond the tool name.

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 the schema already documents all 10 parameters. The tool description adds no additional semantic meaning beyond what the schema provides. Baseline 3 is appropriate since the schema handles parameter documentation.

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 is a tautology ('Create ZenTao requirement') that merely restates the tool name 'zentao_create_story'. It does not specify the verb, resource, or any distinguishing purpose beyond what the name already conveys.

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 siblings like zentao_update_story, zentao_delete_story, or zentao_list_stories. The description lacks any context about appropriate usage scenarios or alternatives.

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