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

The description adds meaningful context beyond the annotations: 'Subscription-gated' indicates access restrictions, and 'Returns ATLAS evidence envelopes only; raw SQL is never returned' discloses output format and a strong guarantee about no SQL leakage. This goes beyond the readOnly/idempotent hints.

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 two short sentences that are front-loaded with the core purpose ('Subscription-gated governed semantic query') and immediately convey the key output constraint. No redundant or unnecessary wording.

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 the presence of an output schema, rich annotations, and fully documented parameters, the description is minimally sufficient but lacks usage context (e.g., when to choose this over compile_query, what 'governed' implies for permissions). It does not fully address navigation among the many sibling 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?

The input schema already describes all 6 parameters with meaningful descriptions (e.g., 'Optional validated sort fields', 'Allowlisted semantic intent'), so the tool description does not need to add parameter-level details. As schema coverage is 100%, a baseline score of 3 is appropriate.

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 states it is a 'semantic query' that returns 'ATLAS evidence envelopes only,' which specifies the tool's action and output. It distinguishes from raw SQL tools by clarifying output, but the exact scope ('evidence envelopes') is somewhat narrow and not differentiated from sibling tools like atlas7_compile_query.

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?

No explicit guidance on when to use this tool vs alternatives. The description mentions 'Subscription-gated governed' but does not state when this tool is preferred over atlas7_compile_query or other query tools, nor any exclusions or conditions.

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