Get latest CDN troubleshoot

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and network profile are covered. The description redundantly echoes the read-only nature with the '[READ]' tag and pins the description to a concrete endpoint, which is mildly useful but adds little behavioral context beyond the 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 short clauses, front-loaded with the action, then the API mapping. Nothing wasted, though the '[READ]' tag duplicates the annotation.

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?

No output schema exists, so the description carries the burden of conveying what a 'troubleshoot' contains (status, findings, timestamps) and whether one may not exist for a domain. It does neither, though the endpoint mapping partially compensates for a tool this simple.

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?

Single parameter with 0% schema description coverage — the schema only supplies a regex pattern and length bounds, not meaning. The description implies a domain identifier via the endpoint template '/domains/{domain}/...', which adds a little semantics, but does not clarify the required format or whether a subdomain is acceptable.

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 ('Get') and resource ('latest troubleshoot for a domain'), and the word 'latest' distinguishes it from list_troubleshoots. It stops short of explicitly naming that sibling or create_troubleshoot as the alternative, but the purpose is unambiguous.

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 statement of when to use this versus list_troubleshoots (all troubleshoots) or create_troubleshoot (generate a new one). The 'latest' qualifier implies the selection condition, but the agent must infer it.

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