get-synthetic-results

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

No annotations are provided, so the description must carry the full burden. It states returns 'individual check results with timing data' implying a read operation. However, it does not disclose pagination, limits, or error behavior, which are important for an AI agent.

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?

Three sentences: function, usage context, output summary. No redundant words, every sentence adds value. Perfectly sized for an AI agent to quickly grasp.

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?

Given 4 parameters, no output schema, and a large sibling list, the description provides essential context: what it does, when to use, and what data is returned. It could mention the timing parameter usage and probe filtering, but it is still fairly complete for a data retrieval tool.

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 input schema covers all 4 parameters with descriptions, so schema coverage is 100%. The description does not add extra meaning beyond the schema; it only reinforces the tool's purpose. 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 clearly states it returns execution results for a specific synthetic test, including pass/fail history, response times, and probe locations. It differentiates from sibling tools like get-synthetic-tests by specifying 'for a specific test' and mentioning the data returned.

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?

The description explicitly tells the agent to use this tool after get-synthetic-tests, providing clear context for when to invoke it. It does not explicitly state when not to use, but the sequencing guidance is strong.

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