get_service_account

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this is a retrieval operation but doesn't disclose authentication requirements, rate limits, error conditions, or what 'details' include. The description is too vague for a mutation-sensitive agent.

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 appropriately concise with two sentences: one stating the purpose and one explaining the parameter. The parameter explanation is detailed but necessary given the schema gap. Minor deduction for the slightly verbose parameter explanation format.

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 has an output schema (which handles return values) and only one parameter (well-explained in the description), the description is reasonably complete. However, the lack of behavioral context (especially with no annotations) and usage guidelines leaves gaps for an agent needing to operate this tool effectively.

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 significant value beyond the input schema, which has 0% description coverage. It explains the 'id' parameter's purpose, format (uuid), and two methods to obtain it (UI URL or lookup endpoint), fully compensating for the schema's lack of documentation.

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 the verb ('retrieves details') and resource ('specified service account'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'lookup_service_accounts' or 'get_account_info', which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'lookup_service_accounts' (which might list accounts) or 'get_account_info' (which might retrieve different account details), leaving the agent with no context for tool selection.

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