get_my_account

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false. The description adds a genuinely useful behavioral trait beyond them: 'Returns live data — not cached from session start,' telling the agent the result is fresh rather than session-stale.

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?

Front-loaded with the resource and returned fields, and the usage triggers come next. The trailing parenthetical '(User account status & credit balance lookup.)' largely restates what precedes it, a minor redundancy.

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 no output schema, the description carries the return-value burden and does so by listing the four returned data categories. Auth/permission requirements are not stated, a small gap for an account-scoped tool, but overall the definition is sufficient to invoke correctly.

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?

Zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description's enumeration of returned fields compensates adequately for the absent output schema.

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?

States a specific verb (check) and resource (current user's account), then enumerates exactly what is returned: API call balance, plan, enabled/disabled graphs, and profile info. This clearly distinguishes it from siblings like list_graphs, get_capabilities, and get_my_earnings.

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?

Gives concrete when-to-use triggers with sample user questions ('how many API calls do I have?', 'what plan am I on?'), which is strong routing guidance. It does not name alternative tools or exclusions, so it stops short of the 5 bar.

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