pls_create_tag

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

Annotations indicate a write operation (readOnlyHint=false) and potential side effects (openWorldHint=true), but the description adds no additional context. It does not disclose authentication requirements, reversibility, or consequences of incorrect usage beyond repeating the confirm requirement already in the schema.

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 short but includes the purpose, parameter list, return format, and a hint. It is front-loaded with the purpose and avoids unnecessary details. Some formatting (emoji, line breaks) is acceptable but not ideal.

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 10 parameters and no output schema, the description lacks sufficient detail. It does not explain what constitutes a 'tag entity', which fields are required for creation vs. update, or provide examples. The vague instruction '根据实体类型传入对应字段' does not sufficiently guide the agent.

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 coverage is 100%, so the base is 3. The description only highlights the confirm parameter and says '根据实体类型传入对应字段' (pass corresponding fields based on entity type), which adds minimal value beyond what the schema already provides.

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 tag entity), using a specific verb and resource. It distinguishes from sibling tools like update, delete, and list, making the purpose unambiguous.

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 no guidance on when to use this tool versus alternatives (e.g., pls_update_tag, pls_delete_tag). There is no mention of prerequisites, conditions, or exclusion criteria. The hint '确认+只传必填字段' is operational, not comparative.

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