load_atlas

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

The description discloses that non-bundled atlases are fetched and cached, which is relevant behavioral context. No annotations are provided, so the description covers the safety profile (read-only load). It could be more explicit about read-only nature but is sufficient.

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 three sentences plus argument details, with each sentence contributing purpose, usage importance, and parameter details. It is front-loaded with the core action and has no 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 the tool's simplicity (one parameter) and no output schema, the description covers what is returned (full label list) and why it matters. It is complete for an agent to understand and use correctly.

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 schema has no parameter descriptions (0% coverage), but the description lists all valid values for 'atlas_name' and explains caching behavior for non-bundled atlases. This fully compensates for the missing schema descriptions.

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 'Load an atlas and return its full label list,' specifying the verb and resource. It distinguishes from siblings like 'load_volume' by focusing on atlases and labels, and explains the role of the label list in grounding region names.

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?

The description tells when to use the tool: before referencing regions, emphasizing that labels from this tool must be used over the agent's own knowledge. It lists valid atlas names. However, it does not explicitly mention when not to use it or compare to alternatives.

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