chainvectorLeadLag

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

No annotations are provided, so the description carries the transparency burden. It discloses the method (cross-correlation over a rolling window) and adds the behavioral insight that laggards follow within seconds. However, it does not describe output structure, data sources, or the fact that it is a read-only operation.

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 two sentences long with no filler. The first sentence states the tool's function, and the second provides actionable context for interpreting results. Every word earns its place.

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 the absence of an output schema, the description should clarify what the returned matrix contains (e.g., rows/columns, values, or ranking). It explains the concept and use case but leaves the exact output format ambiguous, which prevents a higher completeness score.

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?

Both parameters are fully described in the schema (100% coverage), so the description need not repeat them. The description adds no extra semantic detail beyond mentioning the rolling window, which already aligns with the 'window' parameter. Thus a baseline score of 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?

The description clearly identifies the resource (lead-lag matrix) and states its purpose: determining which venue's price moves first for an asset. It distinguishes itself from sibling tools by focusing on cross-venue lead-lag relationships, though it lacks an explicit action verb like 'computes' or 'returns'.

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 implies usage context: to identify leader venues and anticipate follower moves within seconds. However, it does not explicitly state when to use this tool over other chainvector analytics or provide exclusion criteria, earning a middle score.

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