Get team session

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

Describes the snapshot's contents in detail, implying a read-only operation with no side effects. However, it does not explicitly state it is non-destructive or mention authorization requirements, which would improve transparency given no annotations.

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?

Two sentences, zero wasted words. The first defines the tool's output, the second advises when to use it. Perfectly front-loaded and succinct.

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?

Provides sufficient detail about what the snapshot includes and when to call it. Given no output schema, it covers the return value well. Could mention if it requires authentication or if it returns only current data, but it remains complete for the tool's purpose.

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 exist in the schema, so the description naturally cannot add parameter details. With 100% schema coverage and zero params, a baseline of 4 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 clearly defines the tool as a snapshot of team shared context, listing specific components (scope, active users, decisions, locks, inbox messages). It distinguishes from siblings like broadcast or recall which handle messaging or storing information.

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?

Explicitly advises 'Call this at the start of every session,' providing clear usage context. Lacks exclusion criteria or alternative suggestions but adequately guides when to use.

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