get_account_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Read-only', which indicates no mutation but does not cover other behavioral aspects (e.g., authentication, error handling, data freshness, or rate limits). This is minimal transparency.

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 superfluous information. It front-loads the key resource and fields, followed by the read-only trait. Every word contributes value.

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, the description should describe the return format. It lists fields (balance, sequence, flags, regular key) but does not specify the structure or data types. The description is insufficient for an agent to fully understand the output, though the tool is simple.

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 description adds no information about the parameters 'address' or 'network'. The schema covers 50% with a description for 'address', but the description fails to compensate for the undocumented 'network' parameter or add any semantic context 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 clearly indicates the tool retrieves account root information including balance, sequence, flags, and regular key. It explicitly states 'Read-only', distinguishing it from mutation tools. The verb 'get' is implied, and the resource 'account root' is specific, differentiating from sibling tools like get_account_objects or get_account_lines.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention when-not-to-use or provide context for selecting this over other account-related tools. The 'Read-only' hint is the only implicit usage guide, but it lacks explicit comparisons to siblings.

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