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

The description explicitly states 'Execution: synchronous' and 'Task support: forbidden,' and reveals that the output is 'internal application state,' all of which go beyond the annotations. It also provides concrete handling rules (never display raw JSON unless asked, use assistantSummary first) that add behavioral context without contradicting annotations.

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 compact paragraph but mixes core tool semantics with lengthy output-presentation instructions. The 'Classification: read-only' line is redundant with the annotations, making the structure less efficient than it could be.

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 27 undocumented parameters and no output schema preview in this assessment, the description is inadequate for understanding the tool's operation. It explains neither what 'vertical intelligence' is nor how inputs relate to outputs, leaving a massive functionality gap.

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 has 27 properties with zero descriptions, and the description does not mention any parameter or hint at how to fill them. With 0% schema description coverage, the description completely fails to compensate, leaving the agent without any semantic understanding of inputs.

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 begins with 'get vertical intelligence' which merely restates the tool name without defining what 'vertical intelligence' actually is or what it does. The added context that the returned JSON is 'internal application state for LeanrIQ and ChatGPT orchestration' hints at a purpose but remains too vague to distinguish it from sibling tools like leanriq_get_vertical_intelligence.

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 call this tool versus alternatives, what problems it solves, or any exclusions. The only usage-like instruction is 'Use assistantSummary first when responding to the user,' which addresses post-call response formatting, not tool selection.

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