List Webhound Sessions

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

Annotations (readOnlyHint, destructiveHint, idempotentHint) already indicate this is a safe, read-only operation. The description adds 'recent' but does not clarify ordering or pagination behavior. Since annotations cover the safety profile, the description provides marginal additional value, warranting a 3.

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, concise sentence with no wasted words. However, it could be slightly expanded to include parameter hints without becoming verbose. Nonetheless, it is efficiently written.

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?

Despite having an output schema and multiple optional parameters, the description is too sparse. It does not explain what 'recent' means, default ordering, or how to filter sessions. The tool's complexity demands more context for effective use.

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 coverage is 0%, and the description does not explain any of the four parameters (page, type, limit, status). With enums for type and status, the description should clarify their meaning to help the AI agent use them correctly. The lack of parameter information is a critical deficiency.

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 the verb 'List' and resource 'Webhound sessions'. However, it does not differentiate from sibling tools like webhound_search_sessions or webhound_get_session, which could cause confusion about which tool to use for listing vs searching or retrieving a single 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?

No guidance on when to use this tool versus alternatives, no 'when not' or prerequisites mentioned. Given the many sibling tools for specific actions (search, get, export, etc.), the lack of usage context is a significant gap.

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