crm_extract_complete_picklist_hierarchy

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

With no annotations, the description carries the full burden. It discloses a key behavioral trait: the tool is optimized to reduce multiple API calls to a single request. However, it does not reveal details about return value structure, potential side effects, or limitations. It adds some value but is not rich.

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?

One concise sentence front-loads the action and the key benefit. Every word earns its place, with no fluff or repetition.

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?

The description is short but adequate for a straightforward extraction tool. The schema covers parameter semantics, and the description explains the 'one call' consolidation aspect. While no output schema exists, the purpose is clear enough for an agent to select and invoke this tool 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?

Schema description coverage is 100%, so all four parameters are already documented. The description adds no additional parameter-specific meaning beyond what the schema provides. The baseline score of 3 applies.

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 specifies the action ('Extract'), the resource ('complete picklist hierarchy with dependencies'), and distinguishes it from siblings by emphasizing the consolidated single request. It clearly tells the agent what this tool does uniquely compared to other CRM picklist 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?

The description provides clear context for when to use this tool: when you need the complete picklist hierarchy with dependencies and want to avoid multiple API calls. However, it does not explicitly name alternatives or state when not to use it, so it doesn't fully meet the 'explicit when/when-not/alternatives' bar.

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