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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds meaningful context beyond that: it defines the content returned and warns that website capabilities are distinct from MCP tool capabilities, which prevents misinterpretation of results.

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 with no filler, and the primary content list is front-loaded. The enumerated list is slightly comma-ambiguous ('support and affiliate disclosure'), but overall it is tight and appropriately sized.

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 no-parameter, no-output-schema info tool, the description tells the agent what content to expect on return. The only gap is the absence of explicit guidance on when in a workflow to call it versus the search siblings.

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?

The tool takes zero parameters (empty object schema), so there is nothing to document and the baseline is 4. The description adds no parameter detail, and none is needed.

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') and enumerates the resource contents: MCP support, website travel products, support, and affiliate disclosure. It is clear this is a service/metadata lookup, though it does not explicitly distinguish itself from the flight-search siblings by naming them.

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?

Usage is only implied — an agent can infer this is a discovery/capability-check call rather than a flight search, but there is no explicit 'call this first' or 'do not use when' guidance. The note that website capabilities are separate from MCP tool capabilities hints at interpretation but does not state when to invoke it.

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