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

With no annotations provided, the description carries the full transparency burden. It indicates a read operation ('Get') and describes output categories, but doesn't disclose potential caveats like data freshness, permission requirements, or aggregation details. The description is not misleading, but it adds limited behavioral context beyond the name.

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 a single sentence, front-loaded with the verb 'Get', and every word contributes substantive content. There is no fluff or repetition.

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?

The description is brief but covers the core scope (organization statistics) with example categories. Since there is no output schema, the description should detail what is returned; it does so at a high level but leaves room for ambiguity about exact metrics and format. For a stateless read-only tool, this is adequate but not fully comprehensive.

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?

The tool has zero parameters and an empty input schema, so the baseline is 4. The description adds no parameter-specific meaning since there are none, but it does enumerate the types of statistics returned, indirectly clarifying what the tool does.

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 the tool retrieves organization statistics and lists example categories ('counts, engagement metrics, task velocity'), giving a specific verb and resource. It doesn't explicitly distinguish from siblings like get_my_stats or get_team_details, but the org-wide scope is implicit in the name.

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 provides no explicit guidance on when to use this tool versus alternatives such as get_my_stats or get_team_details. It neither states when to choose org-level stats nor mentions any exclusions, leaving usage context implied at best.

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