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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond the annotations by disclosing the return format (Markdown) and the public-page restriction, implying private pages may not be retrievable. No contradiction 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?

Two tight sentences with zero filler. The purpose (what it returns, in what format) is front-loaded, followed immediately by the input requirement and its source. Every word earns its place.

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?

Complete for a single-parameter, read-only tool. It covers the return format, input variants, and slug provenance. The only minor gap is behavior on invalid or non-public slugs (error handling), which is not specified, but this is a small omission for such a simple tool with strong annotations.

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 slug parameter is well documented with examples ('custom_pbx', 'sip-trunk') and the note that a full URL is also accepted. The description adds marginal value by pointing out slugs come from clickphone_cauta, reinforcing the acceptable input forms beyond the schema.

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 and resource: 'Întoarce textul complet al unei pagini publice ClickPhone, în format Markdown' (returns the complete text of a public ClickPhone page in Markdown). The scope is clear and it differentiates from siblings — it fetches page content, whereas cauta searches, cere_oferta requests offers, contact handles outreach, etc.

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?

Provides concrete usage context: it says the slug comes from clickphone_cauta results, which tells the agent how to source the input, and it accepts either a slug or a full URL. It doesn't explicitly name alternatives or state when not to use it, but the sibling tools are functionally distinct enough that purpose alone differentiates them.

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