get_user_person_collections

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe read behavior, but the description adds no further context (e.g., what type of data is returned, pagination, or any caveats). It misses an opportunity to clarify behavioral traits beyond the annotations.

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 extremely brief (one short phrase), which is concise but under-informative. It could be expanded within the same length to add meaningful context, so it scores average on conciseness.

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 (1 parameter, output schema exists, rich annotations), the description lacks essential context such as the definition of 'person collections', list ordering, pagination behavior, or typical use cases. It feels incomplete for an AI agent to use effectively.

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 only parameter 'username' is fully documented in the input schema (100% coverage with description 'username/ID'). The tool description does not add any additional semantic value, but the schema itself suffices, meeting the baseline for this dimension.

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 is a Chinese translation of the tool name, essentially restating 'get user person collection info list'. It provides no differentiation from siblings like 'get_user_person_collection_info' or 'get_user_collections', and lacks specificity about what a 'person collection' entails.

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 alternative tools such as 'get_user_person_collection_info' (likely for a single item) or 'get_user_character_collections'. The description does not mention any use cases or conditions.

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