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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description contributes the 'connected user' scoping (no user id needed) and hints at the returned content, but says nothing about freshness, authentication requirements, or error behavior.

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 short sentence with zero filler, and the key scoping fact (connected user) is front-loaded. It reads as a fragment rather than a sentence with a verb, which slightly weakens actionability.

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 parameterless read with no output schema, the description does the essential job by listing the three returned data points. It stops short of describing format or limits (e.g., what 'daily refresh quota' values look like), which would have made it fully self-sufficient.

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 takes zero parameters, so per the baseline this is a 4; the description correctly implies no input is needed by tying the result to 'the connected user'.

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 names the resource ('the connected user's account') and enumerates the concrete fields returned: plan, daily refresh quota, published codes count. It is clearly distinguishable from siblings like get_company_codes and list_my_codes, though it is written as a noun phrase with no explicit verb ('returns' / 'retrieves').

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?

There is no indication of when to call this versus alternatives such as list_my_codes or get_company_codes, and no mention of prerequisites like authentication. Usage is only inferable from the fact that it takes no parameters.

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