List sessions

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

Annotations already indicate read-only and open-world behavior. The description adds that results are cursor-paginated, newest first, and filterable by status with specific values. This goes beyond the annotations to clarify ordering, filtering, and pagination strategy.

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?

Two sentences with no fluff. The first sentence front-loads the core action and ordering. The second adds filtering and scope requirements. Every word earns its place.

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?

For a list tool with readOnlyHint and openWorldHint, the description covers pagination, ordering, filtering, and auth scope. No output schema exists, but the purpose is clear enough for an agent to infer return format. No gaps identified.

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 33% (only cursor described). The description adds filter values for status but does not explain cursor or per_page behavior beyond what the schema provides. It partially compensates for the undocumented parameters but does not fully clarify their semantics.

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 clearly states it lists USSD sessions with cursor pagination and newest-first ordering, distinguishing it from siblings like hellio_ussd_get_session (single session) and other list tools. The verb 'list' and resource 'USSD sessions' are specific and unambiguous.

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 mentions the required 'ussd' scope as a prerequisite and implies use for fetching collections. However, it does not explicitly contrast with alternatives like hellio_ussd_get_session, though the context from sibling names makes it clear that this is for listing. A direct 'use this when you need to retrieve multiple sessions' would be better.

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