embed_text

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

Discloses Pro-only requirement, 403 error for non-Pro, cost (~$0.0001/call), and rate limit (30/min per key). Also specifies model (Gemini Flash) and dimensions (768). No annotations provided, so description carries full burden and excels.

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?

Efficiently structured: action, use cases, auth/cost. Every sentence adds value. No fluff.

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?

Covers use cases, parameters, auth, cost, rate limits. Lacks explicit output format (e.g., returns embedding object), but usage context with search tools implies it. Minor gap.

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?

Adds significant meaning beyond schema: explains 'text' as hypothetical answer for HyDE, clarifies task_type enum differences. Schema coverage is 100%, so baseline is 3; description elevates to 5.

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?

Description clearly states 'Embed a text string into a 768-dim Gemini Flash vector' and specifies two distinct use cases: HyDE-style retrieval and direct embedding. It uniquely identifies the tool's purpose among 24 sibling tools.

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 describes when to use each task_type (RETRIEVAL_DOCUMENT for HyDE, RETRIEVAL_QUERY for direct queries) and how to integrate with search tools. Provides complete workflow instructions.

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