Get Account

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

Annotations already declare readOnlyHint=true, and the description confirms this with 'Retrieve'. It adds useful context by specifying 'your account' (self-scoped) and the kind of data returned (wallet address, balance, settings). However, it does not disclose any additional behavioral details such as authentication requirements or rate limits, though the annotations cover the basic safety profile.

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 sentence with no filler. It delivers the core purpose, scope, and examples of returned data in an immediately readable format, earning full marks for conciseness.

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 tool's simplicity (no parameters, no output schema) and the annotations that clarify read-only behavior, the description provides sufficient context: it names the resource, scope, and contents. It could arguably mention that it returns data for the authenticated user's own account, but the phrase 'your...account' already implies this.

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 has no parameters, so the description's mention of what will be returned (wallet address, balance, settings) adds meaning beyond the schema. With zero parameters, the baseline is 4, and the description provides a helpful overview of the conceivable return fields.

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 uses the specific verb 'Retrieve' and clearly identifies the resource as 'your Carbon Copy account details', listing wallet address, balance, and settings. This distinguishes it from sibling tools like get_portfolio or get_positions, which focus on different data domains.

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 implies it should be used when you need the current user's account information, but it offers no explicit guidance on when to prefer it over alternatives like get_portfolio or get_trader. There are no stated exclusions or alternative suggestions, so usage context is implied rather than spelled out.

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