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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not state whether the operation is read-only, what side effects occur, or how the tool behaves. The only behavioral hint is that it returns specific pricing data, but this is incomplete for a tool with zero annotation coverage.

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 extremely short and contains no wasted words. However, it is a fragmented list rather than a structured sentence, which slightly reduces clarity. It is appropriately sized for a simple tool but lacks front-loaded framing.

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 absence of an output schema and annotations, the description should explain return values. It lists 'profiles' and 'price/rate limits' with concrete prices, which is a start, but it leaves 'profiles' ambiguous and does not describe the full shape of returned capabilities. It is minimally adequate but has clear gaps.

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 parameter semantics are not a burden. Per the rubric, zero parameters gives a baseline of 4. The description does not need to add parameter meaning beyond the schema.

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 is a fragment ('Profiles, price/rate limits...') without an explicit verb or sentence structure. While the tool name implies retrieval, 'profiles' is vague and the fragment does not clearly distinguish this tool from siblings like verify_get_credits. The specific pricing details add some clarity, but the overall purpose remains only vaguely conveyed.

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 offers no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or sibling tools to route the agent correctly. It simply lists content without context.

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