share_get_point_transfer_address

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description's contribution beyond that is the fact that the returned value is meant to be shared with a transferring party — useful, but thin given an output schema already documents the return value.

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?

A single short sentence with the resource front-loaded and zero filler; nothing to trim.

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?

With no inputs, a full annotation set, and an output schema present, the definition covers what an agent needs in order to call it. Minor residual gap: it does not say whether the address is stable across calls or tied to the current session/account, which matters for a tool returning something you hand to a third party.

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 takes zero parameters and the schema is empty, so there is nothing about inputs the description could or should explain. Baseline 4 applies.

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?

States a specific verb (获取/get) and a specific resource (我的积分收款地址 / my points receiving address), which clearly separates it from sibling tools like share_create_point_transfer or share_get_points_overview. It does not explicitly name or contrast with a sibling, so it lands just short of a 5.

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 clause "可交给转账方" implies the intended situation — you obtain the address in order to hand it to a counterparty who will send you points. That is an implied usage context rather than an explicit when-to-use/when-not-to-use rule or a named alternative.

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