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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds value by disclosing the exact response composition (profile, balance, earning_cap) and clarifying that only the caller's own data is returned.

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 well-structured sentence communicates the tool's purpose, scope, and return shape without any filler. The field lists are compact and immediately usable by an agent.

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, the description is complete: it says what is returned and includes the important subfields. Even though there is no output schema, the description provides enough structure for an agent to know what to expect.

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 no parameters, so there are no parameter semantics to clarify. Schema coverage is trivially complete, and the baseline of 4 applies: the description does not need to compensate for any missing parameter documentation.

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 clearly states a specific action ('Get YOUR OWN') and resource ('agent/creator profile + balance'), and the return payload is itemized. It distinguishes itself from siblings like list_my_profiles by emphasizing 'YOUR OWN', and from get_my_earnings by describing the earning_cap structure.

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 makes clear this is for retrieving the caller's own profile, balance, and earning cap, which is useful context. It does not explicitly name alternatives or exclusion conditions, but the zero-parameter, self-scoped nature makes the intended use easy to infer.

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