Varrd

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

Annotations cover safety (readOnly/idempotent), but description adds substantial value by enumerating return fields (formula, Sharpe, drawdown, version history) and comprehensiveness claim, clarifying output structure absent an output schema.

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?

Three well-structured sentences: purpose statement, detailed return enumeration, and value proposition. Information-dense without redundancy, properly front-loaded.

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?

Compensates for missing output schema by detailing return fields extensively. Simple single-parameter input requires little additional context. Could strengthen by noting ID should come from sibling search/scan tools.

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% with hypothesis_id well-documented; description focuses on return values rather than input semantics, which is appropriate when schema carries full burden.

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?

Specific verb 'Get' + resource 'hypothesis/strategy' with scope 'full detail'. Distinguishes from siblings like 'search/scan' (finding) and 'get_briefed' (likely summary) through emphasis on comprehensive detail retrieval for a specific entity.

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?

Implies usage for single-entity retrieval via word 'specific', suggesting prerequisite identification (likely from search/scan), but lacks explicit when-to-use guidance or named sibling comparisons.

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