gmb_accounts_accounts_get

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds behavioral context by disclosing the NOT_FOUND error for nonexistent accounts or insufficient access rights. This goes beyond the annotations and clarifies the error semantics.

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, front-loaded sentence that directly conveys the operation and a key error condition. Every word earns its place; no unnecessary filler.

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 simple GET operation, the description is adequate. It names the resource, the operation, and an error case. No output schema is present, but the return value ('the specified account') is implied. It could explicitly state that the response contains the account, but the current wording is sufficient.

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?

Schema description coverage is 100%, so the parameters are fully documented in the schema. The description does not add additional meaning beyond what the schema provides; the 'name' parameter is briefly referenced in the path template but not elaborated.

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 states 'Gets the specified account' with a specific verb and resource, clearly indicating a fetch operation for a single account. It differentiates from list/create/patch siblings by focusing on fetching one account by name.

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?

Usage is implied: use to fetch a specific account by name. No explicit alternatives or exclusions are stated. The description does not mention when to prefer other tools like accounts_list, but the singular 'specified account' suggests the intended use case.

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