atlas_lead_lag

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

No annotations provided, so description carries full burden. Describes return type (lead/lag pairs with cross-correlation lag and strength) and that it lists other countries with precedence/following behavior. Adequate for a read-only list tool, but doesn't disclose any safety or authentication constraints.

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: the first states the action and result, the second provides context. No fluff or redundancy.

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 one parameter and no output schema, the description explains what the tool returns (lead/lag pairs, lag, strength) and its application (contagion analysis). Could specify if results are limited, but generally complete.

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 100% schema coverage. The description adds no extra meaning beyond 'for a given country'. Baseline 3 is appropriate.

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?

Clearly states the tool lists lead/lag pairs for a given country, specifying the verb 'list' and the resource 'lead/lag pairs'. Distinguishes from siblings like atlas_contagion_chain which shows chains, and atlas_country_similarity which measures similarity.

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?

Provides context 'for a given country' and 'useful for contagion analysis', but lacks explicit guidance on when not to use or alternatives. Implicitly clear but no exclusions or when-not advice.

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