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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safe read-only nature is well covered. The description adds meaningful behavioral context by specifying that the data is for the 'current authenticated user' and enumerating the quota-related fields (subscription tier, remaining AI tokens, CV credits), which clarifies the scope and statefulness of the returned values beyond 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, tightly scoped sentence that front-loads the verb and resource, then lists the key data points. Every phrase earns its place, with no filler, repetition, or redundant restatement of the title or annotations.

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?

Given the tool's low complexity (zero parameters), the presence of a full output schema, and complete safety annotations, the description is sufficiently complete. It tells an agent exactly what data will be returned (profile, tier, token balance, CV credits) and does not need to explain return values because an output schema exists. No critical information for correctly invoking this tool 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 tool has zero parameters and the schema is essentially empty, so there is nothing for the description to add semantically. The baseline of 4 applies because with no parameters, the description's role in explaining parameter meaning is moot, and the description does not omit any required parameter-level information.

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 verb ('Get') and resource ('current authenticated user account profile'), and enumerates the exact data returned (subscription tier, AI token balance, CV credits). This is sufficiently distinct from sibling tools like civify_check_cv_entitlement or civify_get_pay_per_cv_pricing, which focus on specific entitlements or pricing rather than the overall account snapshot.

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 provides no guidance on when to use this tool versus alternatives such as civify_check_cv_entitlement or civify_get_pay_per_cv_pricing. There is no mention of prerequisites, or situations where another tool would be more appropriate. The 'current authenticated user' wording implies self-service account lookup, but no comparative usage guidance is offered.

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