check_session_consistency

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the operation is read-only, whether it requires existing session data, what happens if the session_id is invalid, or what the output format is. 'Review' implies a non-mutating action, but this is weak and unsupported by explicit statements. Significant behavioral aspects are left undocumented.

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 that front-loads the primary action ('Review stored page snapshots') and then lists specific checks in a compact list. It avoids redundancy and is reasonably scannable, though the enumeration of four checks could be broken out for clarity. Overall, it is efficient without being overly terse.

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 tool with no output schema and no annotations, the description is incomplete. It does not explain the expected return value, how results are presented, or how session_id relates to the stored snapshots. The agent cannot fully anticipate what happens after invoking the tool, nor does it know whether the tool is safe to call without side effects. The complexity of the checks (multiple landmarks, DOM path analysis) warrants 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?

The schema description coverage is 0% and the description does not mention the session_id parameter at all. An agent has no information about the parameter's meaning, format, constraints, or whether it is required (the schema marks it as not required, which is misleading for a tool that likely needs a valid session). The description fails to compensate for the schema's lack of detail.

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 states a specific action ('Review') on a defined resource ('stored page snapshots') and enumerates concrete checks (duplicate IDs, heading-level gaps, multiple main landmarks, control name changes). It clearly distinguishes itself from siblings like analyze_reading_order or analyze_alt_text by focusing on cross-scan consistency issues, leaving no ambiguity about its purpose.

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 provided on when to use this tool versus the sibling analysis tools. There is no mention of scenarios that would select this over analyze_control_names or get_session_report, nor any exclusions. The phrase 'across scans' implies a comparative context, but the description does not explicitly state when a user or agent should invoke it.

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