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

Beyond readOnlyHint=true, it discloses access-control behavior: other people's BP exposes only hasBp with no address/contact info, cloud users are only visible when logged in, and cloud=true means a manual relay via send_cooperation_request rather than direct chat. These are non-obvious privacy and gating rules an agent could not infer from the schema or 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 returned contents are front-loaded, followed by privacy caveats and then arrow-style routing, so an agent can scan it in one pass with no filler sentences. The telegraphic style and unexpanded abbreviations (BP) cost some readability, but every clause carries distinct information.

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 single-parameter read tool with no output schema, it covers returned sections, privacy limits, visibility gating, and handoff tools, which is close to complete. Minor gaps remain: the abbreviation 'BP' is never expanded, and there is no indication of limits or pagination on the listed needs/works collections.

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?

There is a single parameter with 100% schema description coverage ('用户 id(cuid)'), so the schema already carries the semantics and a baseline of 3 applies. The mention of the opcmenu://creator/{id} resource path marginally hints that the id is a stable addressable key, but adds no format or validation detail beyond the schema.

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 enumerates exactly what the tool returns for a creator: public profile, works, on-shelf needs, and role, which pins the resource and scope. It does not restate a verb like 'get/fetch', relying on the title for that, but the returned-content list makes the purpose unambiguous against siblings like get_my_profile.

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?

It explicitly routes the agent elsewhere for adjacent intents: openNeeds→get_need/contact_need, works→get_product, real person→start_conversation, own needs→list_my_needs, and cloud=true→send_cooperation_request. Both when-to-use and when-not-to-use (cannot open chat with cloud users) are stated with named alternatives.

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