get_account

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

Discloses read-only nature, that no browser is started, and what data is masked (cookies, password, proxy credentials). No annotations exist, so description carries full burden. Lacks details on error cases.

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?

Two succinct sentences: first covers what the tool shows, second covers behavioral guardrail. No filler, front-loaded with essential information.

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?

Tool is simple with one required parameter and output schema exists. Description covers main purpose and key behaviors. Minor omission: no mention of error handling or edge cases.

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?

Only parameter 'account' is implied by 'one account' but format or semantics are not elaborated. Schema coverage is 0%, so description adds minimal value beyond 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?

Description clearly states 'Show one account's masked config' with specific exclusions (no cookies, no password, proxy credentials masked) and includes cookie-file status. Distinguishes from sibling tools like list_accounts and get_account_health.

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?

Explicitly states 'Read-only — never starts a browser,' providing clear usage guidance. Does not compare with alternatives or provide when-not-to-use scenarios, but the purpose is distinct enough.

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