get_session_state

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly indicates a read-only operation by saying 'Get' and 'returns raw structured data', and it specifies the returned categories. It could go further with auth or failure behavior, but for a read-state tool this is solid.

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 well-organized with clear sections for purpose, triggers, differentiation, and parameters. Every section earns its place, and the most decision-relevant information is front-loaded in the first sentence.

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?

For a simple read tool with no annotations and no output schema, the description is complete enough: it covers what the tool returns, when to call it, how it differs from the main alternative, and the meaning of both required parameters. An agent has everything needed to invoke it correctly.

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?

The input schema provides no descriptions and schema coverage is 0%, so the description must compensate. It does: session_id is explained as the session identifier, and agent_id is described as 'your agent ID' with a must-belong-to-session constraint. This adds meaningful guidance beyond the bare schema fields.

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 states a specific action ('Get the current state of a collaboration session') and identifies the returned content: tasks, agents, and session state. It also distinguishes the tool from session_context by highlighting that this returns raw structured data rather than a formatted narrative.

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?

The description includes an explicit 'AUTOMATIC TRIGGERS' section listing concrete situations for calling this tool, and it names the alternative session_context with a clear differentiation. This gives an agent strong guidance on when to select get_session_state over its closest sibling.

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