autonomous_varrd_ai

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

Annotations include openWorldHint: true, and the description adds context: it draws from knowledge graphs, tests one hypothesis per call, returns complete results (edge/no edge, stats, trade setup), and requires credits. No contradictions with annotations. Slight omission: does not explicitly state that results are not saved or any rate limits, but adequate.

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 well-structured: first paragraph explains the tool, second gives best-for context, third explains output and usage. Every sentence adds value, and it is front-loaded with the core purpose.

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 6 parameters and no output schema, the description covers tool behavior, return values, and credit usage thoroughly. It explains the exploration process and the kind of results expected. Minor gap: no mention of error handling or timeouts, but sufficient for most use cases.

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?

Schema coverage is 100%, so baseline is 3. The description does not add much beyond schema for individual parameters, but the overall context of how parameters (topic, markets, etc.) fit into the exploration process is clear. Acceptable.

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's purpose: 'Point VARRD's autonomous AI in a direction and let it discover edges for you.' It specifies a verb (point, let discover) and a resource (autonomous AI, edges). It also differentiates from sibling tool 'varrd_ai' by noting when to use each.

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 explicit guidance: 'BEST FOR: Exploring a space broadly.' and 'Use 'varrd_ai' instead when YOU have a specific idea to test and want full control over each step.' This clearly indicates when to use this tool vs the alternative.

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