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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, making the safety profile clear. Description adds context that the tool returns a machine-readable catalog with prices and schemas, enhancing transparency about output content.

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 convey the tool's purpose and key details. The first sentence front-loads the core function, and the second adds the optional filter and payment status without superfluous information.

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 read-only catalog tool with no output schema, the description sufficiently explains what the tool provides (prices, schemas, examples) and that it is free. It does not describe response format, but given its simple purpose, the description is adequate.

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 0%, but the description enumerates the valid values for the 'block' parameter (data|statistics|ads|reference), which matches the schema enum. However, it does not explain what each block represents, leaving some ambiguity.

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?

Description clearly states it is a catalog of all paid Telemost tools, listing prices, schemas, and examples. It distinguishes itself from sibling tools which are individual functional tools (e.g., telemost_ads_networks, telemost_stats_channel).

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?

Description mentions 'Free' and 'No payment required', implying use for discovery before using paid tools. However, it does not explicitly state when not to use or mention alternative tools for specific actions.

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