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

Beyond readOnlyHint, the description discloses that login is required, that the response includes private personal data, and that external sharing needs confirmation. These are important behavioral and privacy caveats that the annotations alone do not convey.

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 compact and front-loads the core read operation, with useful caveats following. It is dense and semicolon-delimited, making it slightly harder to parse, but no sentence is clearly wasted.

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 tool with no output schema, the description supplies enough context: what is returned, the login requirement, privacy handling, and related tools for updating or following up. Nothing essential for correct invocation appears to be missing.

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, so there is no parameter semantics to document; the baseline for a parameterless tool is 4. The description appropriately focuses on returned card contents and usage context instead.

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 uses a specific verb and resource: read the complete personal card, and it enumerates the card contents such as canOffer, group link visibility, products, roles, followed products, and missing items. This distinguishes it from adjacent profile-reading siblings like get_my_profile and get_my_brief.

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 states the login prerequisite, warns that external sharing requires confirmation, and points to update_my_profile/set_my_role_profile for filling in card gaps. It also names a related flow, list_needs_feed→contact_need→send_message, though it does not explicitly say when to choose this over other profile-reading tools.

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