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

No annotations are provided, so the description carries the burden of behavioral disclosure. It lists what the tool returns (credits, channels, delivery counts, manage URL), which gives some transparency about the response, but does not mention side effects, required permissions, or rate limits. A score of 3 is appropriate as it provides minimal behavioral context.

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 concise with a single line that front-loads the key output attributes. It avoids unnecessary words, though it could be structured slightly better with punctuation for readability.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description is insufficiently complete. It lists outputs but does not explain the purpose of the session_token input, any prerequisites, or how to interpret the 'manage URL'. The tool has only one parameter, but the low schema coverage and missing context make it incomplete.

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 there is only one parameter, 'session_token'. The description does not explain the semantics of this parameter beyond its name, leaving the agent with no additional information about what token is required or how to obtain 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 uses a specific verb ('get') with a resource ('session'), and lists key attributes (credits, channels, delivery counts, manage URL) that distinguish it from siblings like get_bundle or get_summary. The purpose is clear and not a tautology.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or context for using the session_token parameter.

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