get_edges

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

No annotations provided, but the description carries the burden well: states read-only, no authentication, no parameters, and explains what the tool returns. Lacks details like data freshness or rate limits, but for a simple data retrieval tool, this is sufficient.

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 sentences with no extraneous words. Front-loaded with the key verb and resource, then adds context and differentiation.

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?

The description explains the return value as 'the edge list' but does not detail the structure of each edge. Given no output schema, a brief field description would improve completeness, but the overall context is clear for a focused 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?

No parameters in the schema, so no param descriptions are needed. The description correctly reinforces that there are no parameters. Baseline for zero parameters is 4.

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 what the tool does: returns current mispricings (edges) across all public theses. Clearly distinguishes from sibling 'get_context' by stating it returns only the edge list, while get_context bundles edges with other data.

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 when to use: for a pure edge list. Provides alternative: use get_context for edges bundled with movers, highlights, and world state. Also notes read-only, no auth, no parameters, giving clear usage boundaries.

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