Get account information

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explicitly notes 'Costs no credits' and enumerates the return fields, providing useful transparency beyond the basic action. It does not mention rate limits or error handling, but for a simple getter with no parameters these are less critical.

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 immediately names the action and resource. It efficiently lists the returned fields and adds a concise cost note. Zero waste.

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?

Since there is no output schema, the description compensates by listing the exact returned fields. It also informs about the credit cost. For a zero-parameter tool, this is sufficiently complete. Minor gaps like error behavior are not significant given the tool's simplicity.

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 is empty (0 parameters), so the baseline is 4. The description adds context by specifying that the account is identified via the 'current API key', which is an implicit authentication input. No parameter details are needed since there are none.

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 the tool 'Return the account profile for the current API key' and lists specific fields (email, name, company, timezone, credits, etc.). This specific verb+resource combination distinguishes it from sibling tools like get_credits or get_usage, which focus on narrower data subsets.

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 implied usage is evident from the resource description ('current API key'), but there is no explicit guidance on when to use this versus alternatives like get_credits or get_usage, nor any exclusions. The context is clear but the guidance is only implicit.

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