zentao_get_user

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

With no annotations, the description must fully disclose behavioral traits. It only states 'get user info' without detailing authentication needs, rate limits, or what specific information is returned. This lack of transparency merits a 2.

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 a single concise sentence that clearly communicates the tool's purpose. It is front-loaded and contains no extraneous information, exemplifying 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 simplicity (one parameter, no output schema), the description is insufficient. It does not mention what user information is returned or any constraints. For a read operation, more context (e.g., fields returned, authentication) would improve completeness.

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 already covers the single parameter 'id' with a description ('用户 ID'), providing 100% coverage. The description adds no additional semantic meaning beyond what the schema offers, so 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 indicates a read operation for user details. It distinguishes from sibling tools like zentao_list_users (list all) and zentao_create_user (create), but does not explicitly differentiate from zentao_get_my_profile. The verb+resource is specific, earning a 4.

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 is provided on when to use this tool versus alternatives, such as zentao_list_users or zentao_get_my_profile. There is no mention of prerequisites, context, or exclusions, resulting in a low score.

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