should_use_atlas_vision

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

Explains the core logic: returns false for models with native vision, true for text-only models with image references. Lacks details on error handling or edge cases, but the logic is well explained given no annotations.

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?

Extremely concise: two sentences that front-load the purpose and provide key return behavior. Every sentence adds value.

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 the primary use case with return value details. An output schema exists, so return structure is handled. Lacks explanation of failure modes or unknown model handling, but is sufficient for a simple routing 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?

With 0% schema coverage, the description only hints at 'main_model_ref' but does not explain the other parameters ('message_text', 'supports_vision'). This is a notable gap for an agent to understand the full input.

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: to check whether Atlas Vision tools should be called based on the main model's capabilities. It distinguishes itself from sibling tooling actors by serving as a prerequisite router.

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 advises calling this before other Atlas tools when routing is unclear. Implicitly discourages use when main model supports native vision, but does not fully elaborate on when not to use.

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