Get RIPE Atlas Measurement Details

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint (safe read). The description adds behavioral context by specifying the return includes 'type, target, status, probes, timestamps', which goes beyond annotations. No contradictions.

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?

The description is concise (two sentences for purpose, two parameter lines, one return line). Information is front-loaded, well-organized with Args and Returns sections. No unnecessary words.

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 read-only tool with full schema coverage and rich annotations, the description is complete. It covers input (parameters), output (return fields), and the nature of the operation. No output schema exists, so describing the return type is appropriate.

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%, so baseline 3. The description lists parameters (measurement_id, response_format) but adds minimal additional meaning beyond the schema descriptions (e.g., 'The measurement ID' vs schema 'The measurement ID to retrieve'). No constraints or examples beyond enum and default.

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 clearly states 'Get detailed information about a specific RIPE Atlas measurement by ID', specifying verb (get), resource (measurement details), and scope (by ID). It distinguishes from siblings like atlas_list_measurements (lists), atlas_get_results (returns results), and atlas_stop_measurement (mutations).

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 explicit guidance on when to use this tool versus siblings (e.g., atlas_list_measurements for overviews, atlas_get_results for raw data). The description implies it's for a single measurement's details, but does not state when-not-to-use or alternatives.

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