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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses the output format (full page as Markdown) and that the empty-slug path returns a different, abbreviated shape — useful context the annotations do not carry.

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?

Two short sentences, no filler. The primary mode is front-loaded and the edge-case mode (empty slug) follows immediately after.

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?

For a single-optional-parameter read tool with no output schema, the description covers what is returned (Markdown page), the alternate mode (listing with short descriptions), and the trigger for it. Nothing an agent needs in order to call it correctly is missing.

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 100% and the enum documents all 17 valid slugs, so the schema does most of the work. The description still adds value by explaining the omitted-slug behavior, which is not representable in the enum (the empty value isn't a listed enum member).

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 gives a specific verb and resource ('Get the full Vocenya page for a product or solution') and names the return format (Markdown). It implicitly separates itself from get_article and get_industry by specifying product/solution pages, but it never names those siblings explicitly.

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?

It clearly documents the second mode of use: leaving the slug empty lists every product page with a short description, which is a genuine when-to-use signal an agent cannot infer. It does not, however, route the agent away from alternatives like get_article or search_articles when those are more appropriate.

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