atlas_ooni_test_diagnostic

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

Describes what the tool provides (test types, volume, gaps) but no annotations present. No mention of side effects, permissions, or return format. Acceptable for a simple read diagnostic.

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 concise sentences, front-loaded with main purpose. No extraneous text.

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 single parameter and no output schema, description sufficiently explains what the diagnostic returns. Mentions key outputs: test types, volume, gaps.

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?

Only one parameter (country_code) with schema description at 100%. The tool description adds context about what the diagnostic covers, but parameter meaning is already clear from schema.

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?

Describes specific verb (diagnostic) and resource (OONI test coverage for a country). Clearly distinguishes from siblings by focusing on test types, measurement volume, and coverage gaps.

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?

Explicitly states use case: assess how well-observed a country is. Implies when to use but lacks explicit when-not or alternative tool references.

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