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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds meaningful behavior beyond that: it returns the complete article body plus a canonical url, and the agent is instructed to attribute that url whenever the content is reused — a real constraint that annotations cannot express.

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 compact clauses that front-load the purpose, then the identifier, then the attribution rule — no filler. The only minor weakness is that the citation instruction arrives abruptly with no framing of what 'the canonical url provided' refers to for an agent that has not yet seen a response.

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 one-parameter, read-only lookup with no output schema, the description covers what the agent needs: what comes back (full article content), how to select it (slug), and the attribution obligation. The language mismatch (Thai description, English tool/sibling names) and the unstated search_articles-to-slug workflow are the only residual gaps.

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 is a single required parameter with 100% schema coverage, and the schema already explains the slug format and that it comes from search_articles. The description only restates that the item is identified by slug, adding no format, length or sourcing detail beyond the schema — the baseline 3 applies.

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 ('อ่านเนื้อหาเต็ม' – read the full content) and a specific resource (CODENIVERSE Insights articles), plus the identifier used to select one (slug). It implicitly separates itself from search_articles by emphasizing 'full content' rather than search, but never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Use is implied: you fetch one article by slug, and the citation rule ('always cite the canonical url') gives conditional output guidance. However, the description never says when to reach for this instead of search_articles or get_page, nor any prerequisite such as 'obtain the slug from search_articles first' — that hint lives only in the schema, not the description.

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