tokportal_get_account

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description doesn't need to repeat those. However, it adds no context about what 'account' means, what 'delivered' implies, or any side effects. The description provides no extra behavioral context beyond the annotations.

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 wasted words. It's front-loaded with the verb and resource. However, it lacks any additional structured information like examples or related tools, which is acceptable given its brevity.

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 a simple single-parameter getter with good annotations, so it doesn't need extensive description. However, the term 'delivered' is ambiguous, and there are many account-related sibling tools. Without clarifying what type of account this refers to (e.g., in contrast to tokportal_get_bundle_account), the description feels incomplete for an agent to reliably select it.

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?

There is only one parameter ('id'), and the schema description says 'Saved account ID.' with full coverage. The tool description adds nothing beyond the schema, so the baseline score of 3 is appropriate.

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.' specifies a verb and resource, but it's quite vague. It doesn't clarify what 'delivered' means in context, and among many sibling tools that start with 'tokportal_get_*', the differentiation is minimal. The title repeats the description, adding no extra clarity.

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?

There is no guidance on when to use this tool versus alternatives like tokportal_get_bundle_account or tokportal_get_account_managed_subscription. It doesn't mention prerequisites or when not to use it, leaving the agent to infer from the name alone.

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