query_session

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

No annotations provided, so description carries full burden. It suggests read-only behavior ('digest'), but does not explicitly confirm idempotency, side effects, error conditions, or auth requirements. The term 'fast' hints at performance but lacks behavioral depth.

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?

Extremely concise: one sentence plus an example. Key purpose is front-loaded ('Fast page digest for LLM navigation decisions'). No redundant words.

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?

Adequate for a simple query tool with one parameter and no output schema. Lists expected fields in return, but lacks detail on format, pagination, error handling, or what happens for invalid session. The example aids understanding.

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?

Input schema provides full description of sessionId ('Session id from start_session'), and description adds an example of its format. With 100% schema coverage, incremental value is limited; description does not explain sessionId further.

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 clearly states it provides a 'page digest' for LLM navigation decisions, listing specific fields (url, title, viewport, ariaSnapshot, interactive controls). The verb 'query' and resource 'session' are specific, but it does not explicitly differentiate from sibling tools like 'query_sessions' or 'orchestrate_session'.

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 quick navigation decisions via 'Fast page digest for LLM navigation decisions', but no explicit guidance on when not to use or alternatives. Lacks prerequisites or conditions (e.g., session must be active), though sessionId is required.

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