pls_create_person

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

Annotations already indicate non-read-only, non-idempotent, non-destructive. The description adds the requirement for secondary confirmation via confirm parameter and specifies return format, which goes beyond annotations. However, it doesn't discuss idempotency or duplicate creation behavior.

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 concise with a header, parameter summary, return format, and tip. It uses few words, but the parameter list is somewhat redundant with the schema. Still, it is efficient and front-loaded.

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?

The tool has 7 parameters and no output schema. The description covers the confirm requirement and basic structure, but lacks context on prerequisites like permissions, entity existence handling, or failure modes. It is adequate but not fully comprehensive.

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% with detailed descriptions for all 7 parameters. The description reiterates the confirm requirement and mentions passing fields based on entity type, but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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 person entity) with a specific verb and resource. It implicitly distinguishes from sibling tools like pls_update_person and pls_delete_person.

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 includes a tip to only pass required fields and mentions the confirm parameter, but lacks explicit guidance on when to use this tool vs. similar CRUD siblings (e.g., update vs. create). No alternatives or exclusions are provided.

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