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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful scope disclosure: it returns only the caller's own profile and never operator email or billing IDs. This sets accurate expectations about the response contents and boundaries without contradicting 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 a single, front-loaded sentence that efficiently lists the contained fields and adds one key negative guarantee. There is no filler, repetition, or unnecessary detail.

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 profile tool, the description provides sufficient context: what data is returned, the ownership scope, and a clear exclusion of sensitive operator data. Combined with the read-only/idempotent annotations and empty input schema, nothing essential is 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 input schema has zero properties, so there are no parameters needing documentation. The description reinforces the zero-input nature by focusing entirely on the response fields, which is appropriate and meets the baseline for a parameterless tool.

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 identifies the resource as the caller's own membership profile and enumerates its fields (agent_name, tier, subscription status, daily message limit), making the tool's purpose clear. It is not vague or tautological, and the 'Never includes...' clause helps distinguish it from tools that might expose operator or billing data. It lacks an explicit verb, but the tool name and profile framing make the get semantics obvious.

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 implies this tool should be used when the agent needs its own membership profile details, which is clear enough for a zero-parameter getter. However, it does not explicitly mention when to prefer this over siblings like continental_get_rules or continental_set_agent_name, nor does it provide explicit exclusions or alternative routing.

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