Get team statistics

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

Annotations already declare this is a safe, non-destructive, closed-world read, so the safety profile is covered structurally. The description adds value by disclosing exactly what the payload contains (total/WIP/shipped post breakdowns, DAU/WAU/MAU), but it says nothing about the empty-default teamName behavior or the shape/size of the response.

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?

One sentence, front-loaded with the verb and resource, with every clause contributing concrete return-field information. The field enumeration is dense but earns its place since there is no output schema to describe the payload.

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 single-parameter read tool with no output schema, the description usefully compensates by listing the metrics returned. The remaining gap is the semantics of the empty default teamName, which neither the description nor the annotations explain.

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% and the single parameter is fully documented there, including the 'call esa_get_teams first' hint. The description adds no syntax or format meaning beyond the schema, 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 ('Retrieves') and resource ('team statistics') and enumerates the returned metrics (member count, posts, comments, stars, watches, active users), which cleanly separates it from siblings like esa_get_team_members or esa_get_team_comments. It does not explicitly name a sibling it is distinct from, so it stops short of a 5.

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 offers no when-to-use guidance, no prerequisites, and no comparison to the sibling tools that return adjacent team data. The only routing hint ('Use esa_get_teams first') lives in the schema's parameter description, not here, so the description itself carries no usage direction.

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