Get Account

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

With no annotations provided, the description carries the full burden and explicitly lists the return fields (name, id, list of REST APIs) and describes the call as the 'smallest', giving a sense of lightweight behavior. It doesn't cover error cases or explicitly state read-only, but for a simple get, this is reasonably transparent.

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 two sentences: the first states the core function and return values, the second adds practical usage context. Every word earns its place, making it concise and front-loaded.

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 parameterless account summary tool, the description covers what it returns, why it's useful, and its lightweight nature. No output schema exists, but the enumerated return values (name, id, accessible APIs) are sufficient for an agent to understand the tool's output.

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 description doesn't need to add parameter details, warranting the baseline of 4. The description's mention of the 'configured AccountSID' clarifies the implicit configuration dependency without needing schema elaboration.

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 it retrieves the account summary (name, id, and accessible REST APIs) for the configured AccountSID. This is a specific verb+resource, and the context about confirming auth and scoped APIs distinguishes it from sibling tools that focus on campaigns, catalogs, actions, and reports.

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 notes it is the 'smallest call' and useful for confirming auth, the persona prefix, and scoped APIs, which provides clear context for when to use it. It doesn't explicitly mention alternatives or when not to use it, but the guidance is sufficient for a parameterless getter.

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