parlayapi_account_info

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It clearly indicates a read-only information operation and lists the exact output fields. While it does not mention error cases or authentication requirements, the phrase 'API key currently in use' conveys the required auth context sufficiently.

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, complete sentence with no redundancy. It front-loads the action and immediately lists the relevant returned fields, making it easy to parse quickly.

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?

The tool takes no parameters, has an output schema, and the description lists the expected output fields. There is no missing information that would prevent an agent from invoking the tool correctly or interpreting its purpose.

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?

With zero parameters and schema coverage at 100%, no parameter explanation is needed. The description reinforces that the only implicit input is the currently authenticated API key, adding context beyond the empty 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 states a clear verb ('Get'), resource ('API key currently in use'), and specific data points (tier, credits remaining, billing period). This distinguishes it clearly from sibling tools that focus on odds, sports, pricing, or signup flows.

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 context is clear: use this tool when an agent needs account status, credit balance, or billing period for the current API key. It does not explicitly mention exclusions, but among siblings it is the only account-info operation, so the intended usage is well implied.

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