internal_squad_stats_get_internal_squad_usage

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

With no annotations, the description carries the full burden. It usefully discloses the eventual-consistency window ('usage data is flushed to the database roughly every 2 minutes'), the node scoping rule, and the population of returned users, which goes beyond the schema. It omits auth/permission requirements, response shape, and pagination response behavior (e.g. nextCursor), so it is only partially complete for a no-annotation tool.

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 core purpose is front-loaded, but the entry is a mixed bag: an HTTP route line, a tags line, and a trailing Russian-language sentence ('Пагинация через query-параметры: start, limit.') break structure and language consistency without adding much value.

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 6-parameter, no-annotation, no-output-schema read endpoint, the description covers the semantics of the returned set and data freshness, which is the important part. It leaves the agent without return-format guidance (what fields per user, how cursor/nextCursor is surfaced) and without any indication of auth requirements.

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 the baseline is 3; the description restates the minTotalBytes filter and scoping condition without adding syntax or format detail. Its pagination note is also mildly inaccurate – it names 'start' (a date field) and 'limit' as the pagination query params while the schema's actual cursor token is 'cursor' – which slightly muddies rather than clarifies the parameters.

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 names a specific verb and resource ('Get internal squad users traffic usage for a period') and even pins the HTTP route, so the purpose is unambiguous. It does not, however, differentiate itself from near-identical siblings such as internal_squad_stats_get_internal_squad_user_usage or internal_squad_get_internal_squad_usage, which an agent could easily confuse.

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?

Usage is implied rather than stated: the period requirement and the minTotalBytes threshold hint at when the tool is appropriate, and the ~2 minute flush interval hints at when results may be stale. There is no explicit when-to-use, no exclusions, and no routing to the very similar sibling usage endpoints.

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