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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds meaningful behavioral context beyond annotations: login is required, the tool returns grouped and visibility-tagged data, and the 'missing' field serves as a ready-made completeness checklist. No contradiction with 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 well-structured with labeled sections: content summary, when to use, combination chain, modification routing, and completeness semantics. Despite its length, every section adds practical value and the core promise is front-loaded in the first sentence.

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?

For a zero-parameter read-only aggregation tool with no output schema, the description fully covers what data is returned, when to use it, how to chain it with other tools, and where to go for modifications. Nothing essential is missing for an agent to invoke it correctly.

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 tool has zero parameters and schema description coverage is 100%, so the description has no parameter burden. It correctly implies no inputs are needed and focuses on what the response contains.

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 states a specific verb-resource relationship: one call retrieves the complete structured set of 'who I am' data, enumerating basic info, links with visibility, published products, role profiles, and followed products. It clearly differentiates from sibling getters by emphasizing aggregation ('一次调用拿全') and by naming alternative tools for modifications.

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 explicitly lists when to use this tool (writing openers, filling external forms, generating BP outlines, judging demand fit) and advises against chaining multiple tools for the same data. It also routes modifications to update_my_profile and set_my_role_profile, giving clear alternatives.

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