fastmail_get_account

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

No annotations are provided, so the description must carry the behavioral disclosure burden. 'Get' implies a read-only operation and the description names the return categories, but it does not disclose authentication expectations, session-token sensitivity, or whether any cached state is involved. This is thin but not contradictory.

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?

One sentence, front-loaded with the operation, with no filler. The brevity is appropriate for a zero-parameter getter, and every word contributes to understanding the tool's purpose.

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?

The tool is simple with zero parameters, and the description covers the high-level purpose. However, with no output schema, the agent is left without details on the shape or content of the returned account information and session details. This is adequate for calling the tool but not fully complete for interpreting its response.

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 tool has zero parameters and 100% schema coverage, which is the baseline-4 case; there is no parameter-level meaning for the description to add. The description correctly focuses on the operation rather than inputs.

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 names a specific verb ('Get') and resource ('Fastmail account information and session details'), which clearly separates it from the email, masked-email, and folder siblings. It does not explicitly state how it differs from other account-level operations, but no such sibling exists.

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 guidance is provided on when to use this tool versus alternatives. It simply states what it does, with no prerequisites, exclusions, or context to help an agent decide whether this is the right tool for account-related information.

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