context

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

Describes main behaviors (store, get, assist) and their parameters. No annotations provided, so description carries full burden. Missing details on persistence, side effects, or errors; partially compensates but could be more transparent.

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?

Concise and well-structured with markdown headers and bullet points. Each sentence serves a purpose; no fluff. Efficiently presents three modes and their parameters.

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 core functionality and parameter usage per mode. Lacks description of return values (though output schema exists) and error behavior. With moderate complexity, more detail on outputs would improve completeness.

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?

With 0% schema description coverage, the description adds essential meaning by mapping parameters (conversion_id, context_data, sql_query, selected_text) to specific modes. Could include more detail on expected formats (e.g., context_data as JSON).

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?

Clearly states verb and resource: 'Store, retrieve, and work with SQL/PySpark conversion context.' Lists three distinct modes with specific purposes, differentiating it from sibling tools like convert and analyze.

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 on when to use each mode (e.g., store for additional context, get for retrieval, assist for real-time SQL help). Lacks explicit when-not-to-use or alternative tool references, but usage context is clear.

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