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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, and the description merely repeats 'Classification: read-only.' It does add genuine value by disclosing that the return payload is internal application state and by giving output-presentation rules (prefer assistantSummary, don't show raw JSON, mention IDs sparingly). That output-handling context justifies a 3, though it says nothing about the read's scope, permissions, or size.

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 size is moderate but badly front-loaded: the purpose is a single tautological sentence, while the bulk is generic boilerplate that could be pasted onto any LeanrIQ tool. Sentences do not earn their place relative to the tool-specific information an agent actually needs.

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?

A rich output schema exists, so return values need not be explained, which offsets some burden. However, for a 14-parameter tool with nested objects and zero schema coverage, the description is far too thin on inputs and provides no scoping, filtering, or prerequisite context. It is not complete enough to guide correct invocation.

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?

There are 14 parameters with 0% schema description coverage, and the description provides no parameter information at all. Names like sourceLocale, marketContext, languageVariantGroupId, and requestedOutputLocales are left entirely unexplained. With no schema documentation to lean on, the description fails to compensate for a severe gap.

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 opens by restating the title almost verbatim ('list accessible seats'), which is a tautology rather than an explanation. It never says what a 'seat' is or how this differs from siblings like get_current_seat, leanriq_current_seat, or leanriq_select_seat. An agent gains no discriminating information beyond the tool name.

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?

There is no when-to-use or when-not-to-use guidance whatsoever, and no mention of any alternative such as get_current_seat. The only instructions concern output formatting, not tool selection. An agent cannot tell from this text when this tool is the right call versus its seat-related siblings.

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