Find Manager Chain

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

With no annotations provided, the description bears the burden of disclosing behavior. It indicates a read-only 'Find' operation, which is non-destructive. It does not mention edge cases (e.g., no managers found) or whether the result includes the person themselves, but for a simple query this is acceptable.

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, concise sentence that conveys the essential purpose without any fluff or redundancy. It is well-structured and easily parsed.

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?

For a simple query with one fully described parameter and no output schema, the description plus schema is sufficient for an agent to understand what the tool does. It could optionally mention the output format, but that is not necessary for basic invocation.

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 fully describes the single parameter person_id as 'Person identifier (uid, email, or DN)', giving complete coverage. Since schema coverage is 100%, the baseline is 3. The description adds no extra semantic detail beyond the 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 action ('Find') and the resource ('management chain for a person'), with a clarifying parenthetical ('all managers up to the top'). It is easily distinguished from sibling tools like get_person_details or get_organization_chart, which serve different purposes.

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 implies when to use the tool—when a user needs the full chain of managers rather than a single person's details or a full org chart. However, it does not explicitly mention alternatives or state 'use this instead of X when...', so it falls slightly short of full explicitness.

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