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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds useful behavioral context: it accepts full URLs or paths, handles multilingual domains (projectthunder.mx, pt.projectthunder.com, projectthunder.asia), and notes that the ERP partner directory exists only in English. It also explains language override behavior. No contradictions with 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?

Three concise, front-loaded sentences. The first sentence states the core function and output; the second covers input formats; the third explains language behavior. No redundancy or filler.

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 no output schema, the description fully explains what is returned (Markdown with title, URL, summary, full content). It also covers input variations and language behavior, including the edge case of ERP partner content being English-only. No critical information is missing for an agent to call this correctly.

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%, so both url and language are documented. The description adds value by explaining how the URL host implies a language and how the language parameter overrides that. This clarifies the interaction between parameters, going beyond schema descriptions.

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 states a specific action ('Returns one page or Insights article'), the resource (projectthunder.com pages), and the output format (Markdown with title, URL, summary, full content). It clearly distinguishes itself from listing and search siblings by focusing on retrieving a single page's full content.

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 implies usage for fetching a specific page's full content, contrasting with listing tools like list_pages and list_articles, and search_site for discovery. However, it does not explicitly state when not to use it or name alternatives; the context is clear but not explicit.

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