get_realtime_session_summary

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

No annotations are provided, so the description carries the full burden. It only restates the 'get' action and 'summary' resource without disclosing read-only nature, return contents, time range, or any other behavioral characteristics. 'Get' weakly implies read-only but this is not explicit.

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 short sentence with no redundant wording. It is front-loaded and efficient, though it is so terse that it omits useful context that is penalized under other dimensions.

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?

With only three simple parameters and no output schema, complexity is low, but the absence of any detail about what a 'summary' returns, and no contrast with nearby realtime session tools, leaves the agent guessing. The description is too minimal to be fully actionable.

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 covers all three parameters with basic descriptions (100% coverage), so the description does not need to add parameter details. The description adds no extra semantic information, but the schema already does the heavy lifting.

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 ('Get') and resource ('Realtime Kit session summary'), which distinguishes it from a full session fetch like get_realtime_session. However, it does not explain what the summary contains, leaving some ambiguity about the exact resource shape.

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 on when to use this tool versus closely related siblings such as get_realtime_session or get_realtime_session_transcript. An agent has no basis to decide whether a summary, full session, or transcript is the appropriate call.

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