get_account

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

Annotations already fully declare the tool as read-only, non-destructive, and idempotent. The description adds no behavioral details beyond 'Show', so it does not contribute extra transparency but is consistent.

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?

Single sentence, no extraneous information. Front-loaded with the core action. Perfectly concise for a simple read operation.

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 zero parameters, comprehensive annotations, and no output schema, the description sufficiently conveys the tool's function. It could list the types of metadata returned, but not necessary with annotations.

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?

Tool has zero parameters, meeting the baseline of 4 per guidelines. Description does not need to clarify parameters since there are none.

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 uses 'Show Vultr account metadata', a specific verb-resource pair. It distinguishes from sibling tools like 'create_instance' or 'get_instance' which deal with instances, making the purpose clear.

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?

No explicit when-to-use or alternatives, but the tool's simplicity (no parameters) and unique resource (account metadata) make its usage implicitly clear. Sibling tools target different resources.

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