get_session_stats

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

No annotations provided. Description indicates a read operation but does not disclose potential behavior: no mention of rate limits, error conditions, performance implications, or what happens when no sessions exist. Only lists returned fields without behavioral context.

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?

Description is two short paragraphs with a clear first sentence. The list of returned items is compact. Could be slightly tighter (e.g., no need for 'Returns:' line), but overall efficient and front-loaded with core purpose.

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 zero parameters and no output schema, description explains for the most part what stats are returned. However, it leaves ambiguity: what units for 'size'? what format for 'date range'? Does it include all sessions or filtered by some context? Sibling tools help, but more detail would be helpful.

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?

No parameters, schema coverage is 100% trivially. Description adds value by listing what the return value contains, which is helpful for understanding output even though not strictly parameter semantics. Baseline for zero-param is 4.

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?

Description clearly states verb ('Get statistics') and resource ('Copilot session history'), lists specific aggregates (total count, size, date range, event types, models). Distinguishes from siblings like list_recent_sessions and get_session_conversation which handle individual sessions or lists.

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 explicit guidance on when to use this vs. sibling tools. Lacks statements like 'Use for aggregate overview, not detailed per-session data.' Agent must infer from description of returned data.

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