edges

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

The description indicates the tool returns precomputed data (implying efficiency) and lists edge kinds, but does not disclose other behavioral traits such as permissions, rate limits, or whether the result is mutable. No annotations exist to contradict.

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?

One short sentence plus a comma-separated list of kinds. No redundant words; front-loaded with the core action.

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 presence of an output schema and the tool's simple purpose, the description adequately covers the essential information. It lacks details about edge kind meanings but remains sufficient for an agent to invoke correctly.

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 schema describes all 5 parameters, but the description adds the list of valid edge kinds, which is not in the schema's 'kind' property description. This adds meaningful context beyond 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?

The description clearly states the tool returns precomputed signal edges and lists specific kinds (rise, fall, etc.), which distinguishes it from siblings like 'first_edge_after' and 'changes'.

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 guidance on when to use this tool versus alternatives like 'first_edge_after' or 'changes'. The description mentions edge kinds but does not explain the context for each kind or when to prefer this over related tools.

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