set_external_session_id

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

Description says 'Pass an empty string to clear' but input schema has no parameters, creating a misleading behavioral trait that contradicts the structured schema definition.

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 are concise, but the structure is flawed by implying a parameter that doesn't exist, making the description misleading.

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?

Missing critical context on how to actually provide the session ID; the inconsistency with schema leaves the description incomplete for a parameterless tool.

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 has no parameters (100% coverage), but description implies a string parameter exists, adding incorrect semantics beyond what schema defines.

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 states the tool attaches a session ID to analytics rows and mentions clearing with empty string, but purpose is undermined by contradiction with input schema (no parameters defined).

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?

Implies usage for correlating analytics logs and clearing, but no explicit when-to-use or alternative guidance relative to siblings like session_stats.

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