get_account

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

Beyond the readOnlyHint annotation, the description states 'Read-only' and discloses precise error behavior: returns an error object when ref matches nothing and never raises. This is valuable operational context that the annotation alone does not provide.

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 well-structured: purpose first, then safety/error behavior, then sibling routing, then parameter format. Every sentence adds distinct value, and the format is easy to scan.

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 single-parameter read-only tool with an output schema, the description covers purpose, return contents, acceptable ref formats, error behavior, and alternatives. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 0%, so the description must compensate, and it does thoroughly. The Args section explains the 'name' parameter's accepted forms (full path, %short GUID, full 32-char GUID) with a concrete example, giving an agent the syntax needed to call the tool.

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?

States a specific verb and resource ('Get details for one account') and enumerates the exact data returned (type, commodity, description, placeholder flag, GUID, hierarchy position). It differentiates from get_balance and get_account_slots before those tools are even named by clarifying what this tool does and does not return.

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 routes to alternatives: list_accounts for bulk discovery, get_balance when only a number is needed, get_account_slots for custom metadata. This gives clear when-to-use and when-not-to-use guidance, which is exactly what an agent needs to select among siblings.

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