account_get

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

With no annotations, the description carries the full burden for behavioral disclosure. It only says 'Get details', which restates the tool name and doesn't disclose read-only behavior, error conditions, authentication needs, or response format. The verb 'Get' implies read-only, but that is inherent in the name, so the description adds little beyond structured data.

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 sentence with no filler or redundant phrases. It efficiently conveys the tool's purpose and is appropriately sized for a one-parameter getter.

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 one parameter and no output schema, so the short description is sufficient for basic invocation. However, it could be more complete by explicitly stating that it returns account details or noting the output type, though this is a minor gap for a standard getter.

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 schema already documents the only parameter 'id' as an Account ID, and the description adds no additional meaning or format details. With 100% schema coverage, the baseline of 3 applies, and the description's 'specific account' merely aligns with the schema without enriching it.

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 action ('Get details') and the specific resource ('a specific account'), distinguishing it from sibling tools like account_list that handle multiple accounts. It also names the product context (Toshl Finance) for disambiguation.

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 usage guidance is provided. The description doesn't mention when to use this tool versus account_list or when not to use it, nor does it indicate that an account ID is required. The phrase 'specific account' implies an ID is needed, but no explicit alternatives or exclusions are given.

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