Get CDN acceleration settings

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint. The description adds only the [READ] tag, which echoes readOnlyHint, and a confusing sentence about PATCH bodies that does not clarify behavior of this read operation (e.g., return format, pagination).

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 sentences, front-loaded with the essential HTTP method and endpoint. The second sentence about offline FA documents is cryptic and does not clearly earn its place, making the structure slightly noisy.

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 simple GET tool with annotations and no output schema, the description gives the endpoint and a hint that the settings relate to CSS/JS optimization. However, it lacks parameter semantics and does not describe what the response contains, leaving some gaps for an agent to fill.

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 description coverage is 0% and the single domain parameter has no description. The path template GET /domains/{domain}/acceleration implies the parameter is the domain name, but no format details or constraints are added beyond what the schema pattern already provides.

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 verb and resource with the [READ] tag and GET /domains/{domain}/acceleration, making it clear this retrieves CDN acceleration settings for a domain. It implicitly distinguishes from the sibling update_acceleration by being read-only, but does not explicitly name the alternative.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The only contextual hint is a cryptic mention of offline FA documents for PATCH bodies, which does not tell the agent when to select this tool over siblings like get_caching_settings.

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