tokportal_get_account

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

The annotations clearly indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds minimal behavioral context beyond 'delivered' status, which is not explained. With strong annotations, this scores a 3 as the description adds little extra value.

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, short sentence with no filler. It is front-loaded with the key action and resource. However, the word 'delivered' could be expanded in one additional sentence to clarify the account state without harming conciseness.

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?

With a tool that returns account data and no output schema, the description should clarify what fields or state the returned account includes, especially the meaning of 'delivered'. The sibling tools for account management suggest there are distinct account states or types, and this description fails to contextualize its role.

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 for parameters is 100%, with the 'id' parameter described as 'Saved account ID.' The description does not elaborate further on the parameter. Baseline 3 is appropriate since the schema already documents the single parameter sufficiently.

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 'Get a delivered account.' clearly indicates the action (get) and resource (a delivered account). However, it does not define what 'delivered' means in this context, which could cause confusion. It is minimally adequate but lacks specificity to distinguish from related tools like 'tokportal_get_account_managed_subscription' or 'tokportal_get_account' (if such existed).

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 like 'tokportal_get_account_managed_subscription' or 'tokportal_get_bundle_account'. The term 'delivered' is unexplained, and there are no remarks about prerequisites or contexts where this tool is appropriate.

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