⚠️ Hierarchy: assign listings

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

Discloses irreversibility: 'Irreversible operation (the previous assignment is not restored automatically)'. Also mentions repeated calls reassign and return status is HTTP 204 with no body. Adds significant behavioral context beyond annotations (destructiveHint true).

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?

Three sentences, front-loaded with primary action. Each sentence adds essential detail without redundancy. Perfect structure for quick agent parsing.

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 lack of output schema and irreversible nature, description covers permissions, safety checks (dryRun), idempotency, and prerequisites. Agent has enough to use tool correctly without missing critical context.

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 coverage is 100% with good descriptions. Description adds value by linking employeeId to hierarchy_get_employees_v1 output, providing usage context that schema lacks. DryRun and idempotencyKey are well-documented in schema.

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 assigns listings to an employee within the account hierarchy, using the verb 'assign' and specifying the resource 'listings' and context 'account hierarchy'. It distinguishes from sibling tools like hierarchy_get_employees_v1 by focusing on assignment.

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?

Provides explicit prerequisites: hierarchy permissions, user state check via hierarchy_check_ah_user_v1, and employeeId from hierarchy_get_employees_v1. Tells agent where to get required inputs, though does not explicitly state when not to use (but is implied).

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