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

With no annotations, the description carries the full burden. The phrase 'Account status' hints at a read-only operation, but it does not explicitly state side effects, authentication needs, rate limits, or the nature of the response. Important behavioral traits are missing.

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 very short, but it is a fragment (no verb) and not structured as a complete sentence. While concise, it sacrifices clarity and could be better organized with a front-loaded verb and structured list.

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 description only lists a few data items without explaining return format, interpretation, or the relationship between the session_token and the output. Given the tool's simplicity and lack of output schema, the description is incomplete for effective use.

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 description coverage is 0%, and the description does not mention the 'session_token' parameter at all. The description adds no meaning beyond the schema, failing to explain what the token is or how it relates to the account status data.

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 lists account status components (credits, channels, delivery counts, manage URL) but lacks a clear verb like 'retrieves' or 'returns'. It implies the tool provides account status information, but the purpose is vague and does not distinguish from sibling tools like 'get_summary' or 'get_template'.

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. The description does not mention prerequisites, exclusions, or context for use, leaving the agent without decision support.

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