atlas_analyze_opportunity

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

With no annotations, the description carries the behavioral burden. It does disclose that the tool 'Returns a framework' and describes the approach as 'structured multi-lens,' which is helpful. However, it does not state whether the analysis is persisted, whether it is read-only, or any side-effect expectations.

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 a single, focused sentence that front-loads the core behavior and then states the return value. Every word earns its place; there is no filler or redundancy.

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 no output schema and no annotations, the description should clarify more about what the returned framework contains and whether the analysis is stored. It gives enough to attempt a call, but leaves meaningful ambiguity about the output structure and side effects.

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 description coverage is 100%, so the baseline is 3. The description's mention of career, business, and life changes aligns with the type enum but adds no detail about how 'context' affects the analysis or how the parameters interact.

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 identifies the tool's action ('analysis') and resource ('opportunity'), and it specifies the domains it applies to (career moves, business decisions, life changes). It does not explicitly contrast with siblings, but the purpose is distinct enough from nearby ingest/search 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?

It gives concrete usage context: use this when evaluating a career move, business decision, or life change. It does not state exclusions or point to an alternative tool like atlas_search_advice_history, so it stops short of full routing guidance.

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