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

No annotations are provided, so the description carries full behavioral disclosure burden. It mentions pagination via cursor, which is a useful trait, but does not explicitly state that the operation is read-only, describe the return format, or mention any side effects or limitations. The 'List' verb implies non-destructive behavior, but it is not explicit.

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?

A single, efficient sentence that conveys the core purpose and key filtering options. It is front-loaded with the main action and adds pagination support. While compact, it could list a few more specific examples of filters but remains appropriately sized.

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?

Given 10 optional parameters, no output schema, and no annotations, the description is incomplete. It does not explain the response structure, error behavior, default sorting, or how to iterate through pages beyond mentioning the cursor. An agent would need to infer many operational details before successfully using the 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 description coverage is 100%, so the input schema already documents all 10 parameters. The description adds a high-level summary of filter capabilities ('status, date range, and search term') and mentions cursor-based pagination, which mirrors schema details. No additional semantic value is provided beyond the schema.

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?

States a specific verb and resource: 'List FaceSign sessions' with filtering options. The purpose is clear, but it doesn't explicitly differentiate from sibling get_session, relying on the verb 'list' to imply it returns multiple sessions. This is slightly above 'clear but no sibling differentiation'.

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 over alternatives. The description only lists optional filters and pagination, but doesn't mention any exclusions, prerequisites, or relation to get_session. An agent must infer that this is for collecting multiple sessions vs. retrieving a single one.

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