get_account

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

No annotations exist, so the description bears the full burden of behavioral disclosure. It only lists returned data categories and does not mention read-only semantics, authentication requirements, account scope, data freshness, or potential side effects.

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 compact, front-loaded phrase with no filler or redundancy. Every word contributes meaningful information about what the tool returns, making it appropriately concise for a trivial getter.

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 zero-parameter tool with no output schema and low complexity, the description lists the key return categories (balance, earnings, profile details) which is largely sufficient. It is slightly vague on what 'profile details' encompasses and does not clarify account ownership, but it provides enough context for a basic call.

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 the empty schema is complete and description has no parameter burden. The baseline of 4 applies because there are no parameter semantics to explain.

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 identifies the resource (account) and the specific information returned (balance, available earnings, profile details). It is more specific than a tautology and conveys the core purpose, though it lacks a verb and does not explicitly distinguish itself from sibling tools like get_earnings.

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?

No usage guidance is provided. There is no statement about when to use this tool versus alternatives such as get_earnings or get_statement, nor any exclusions or context for when this tool is appropriate.

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