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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the response carries edge_url and dashboard_url, which is useful return-shape context given there is no output schema, but it does not describe the rest of the payload or whether the call can fail for missing/unknown ids.

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 the payload contents front-loaded and no redundant wording. The second sentence is a follow-up tip rather than core definition, but it earns its place by telling the agent how to act on the returned URL.

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 single-parameter read tool with annotations covering safety and no output schema, the description supplies enough: what is fetched, the key return fields, and how to use the dashboard link. Missing only error behavior for unknown surface ids, which is minor at this complexity.

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 single parameter already documents that surface_id comes from surface_list, so the schema does the heavy lifting. The description adds no format, range, or origin detail beyond that, so the baseline 3 applies.

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: retrieves full details for a single surface, and it implicitly distinguishes itself from surface_list by scoping to 'one surface' and by the surface_id parameter note pointing at surface_list. It stops short of naming the sibling alternative in the description itself.

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?

There is no explicit when-to-use versus when-to-use-alternatives guidance. The only procedural guidance is downstream of the call ('to open the surface in the dashboard, open dashboard_url'), which tells the agent what to do with the result rather than when to choose this tool over surface_list.

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