openwisp_list_radius_sessions

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

With no annotations, the description carries the full burden: it discloses the read-only nature indirectly via 'List' and 'HTTP GET', which is useful. However, it says nothing about pagination behavior (despite a page param), result volume, or authentication requirements, so key behavioral context is 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?

A single front-loaded sentence plus the endpoint reference, with no wasted padding. It is efficient, though the endpoint parenthetical is more structural trivia than agent-relevant content.

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 paginated list tool with no output schema and no annotations, the description is only marginally adequate: it does not describe the return shape, pagination semantics, or what a session record contains. The 100% schema coverage on the three inputs partially offsets this.

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 100%, so all three parameters (page, username, calling_station_id) are already documented in the schema. The description adds no filtering syntax or format hints beyond what the schema provides, so the baseline 3 applies.

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 (List) and resource (RADIUS authentication and accounting sessions) with a clear domain qualifier (WiFi hot-spots and captive portals). It is trivially distinguished from the many device/CA/VPN siblings, and the category tag and endpoint reinforce what is being fetched.

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 on when to use this versus openwisp_get_radius_usage, nor any statement about prerequisites or scope. The only contextual hint is the HTTP endpoint, which does not tell an agent when this tool is the right choice.

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