github_api_insights_get_summary_stats_by_user

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

With no annotations, the description carries full responsibility for behavioral traits. It fails to state that this is a read operation, nor does it mention any side effects, permissions, rate limits, or data scope beyond what is inferred from 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 only four words, which is excessively brief. While concise, it omits critical information and lacks any structure or detail that would help the agent use the tool correctly.

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?

Given the tool has four parameters and no output schema, the description should explain what 'summary stats' includes, the time range behavior, and how it differs from related tools. It fails to provide this context, leaving the agent under-informed.

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?

Input schema has 100% coverage, with each parameter described minimally (e.g., 'org', 'user_id', timestamp format). The description adds no additional context beyond the schema, so the baseline score of 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?

The description 'Get summary stats by user' indicates the tool retrieves summary statistics for a specific user, which is clear but doesn't differentiate from sibling tools like get_summary_stats or get_summary_stats_by_actor. The phrase 'summary stats' is vague, leaving the exact nature of the stats ambiguous.

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 is provided on when to use this tool versus alternatives such as get_summary_stats_by_actor or get_time_stats_by_user. There are no hints about prerequisites, limitations, or best use cases.

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