get_live_sessions

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

With no annotations provided, the description must disclose behavioral traits but does not. It fails to state that this is a read-only operation, clarify what 'currently active' means, or mention any limitations or side effects. The agent is left without crucial safety and behavior 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?

The description is a single sentence with no waste, but it is under-specified. Terms like 'recent' and 'live' overlap with 'currently active,' adding mild redundancy. It lacks a clear verb and feels more like a fragment than a complete instruction.

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 tool is relatively simple but has no output schema, so the description should convey what the returned sessions look like. It does not mention return format, fields, or how 'recent' relates to 'live.' The presence of siblings like get_session_details further underscores the need for more context.

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%, with both appId and buildMode having reasonable descriptions. The schema already explains the parameters, and the tool description adds no extra parameter semantics. According to the baseline rule for high schema coverage, a score of 3 is appropriate.

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 "Recent/live sessions currently active for an app" conveys the resource (sessions) and temporal state (live/active), but it is a noun phrase rather than a clear verb+resource construction. It does not explicitly differentiate from siblings like get_historical_sessions or get_session_details.

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 given on when to use this tool versus alternatives. The description doesn't mention that get_historical_sessions should be used for past sessions or that get_live_geo is for geographical data, leaving the agent to infer the appropriate context.

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