get_org_chart

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

No annotations provided. Description mentions internal data sources (EmpJob, User) and navigation direction, but does not disclose authentication requirements, rate limits, or potential performance implications of depth values.

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 concise sentences, front-loaded with purpose. No redundant information.

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?

Output schema exists, so return value explanation is not needed. Description covers main functionality and data sources, missing only minor details like format representation.

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 50% (3 of 6 params described). Description explains user_id, depth_up, depth_down but not data_center, auth_user_id, auth_password. Partially compensates but not fully.

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?

Description clearly states the tool gets an org chart centered on a specific employee, with specifics about upward/downward navigation. Distinguishes from siblings like get_org_structure.

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?

Description implies use for centering org chart on an employee but does not explicitly contrast with similar tools like get_org_structure or get_employee_profile. No when-not-to or alternatives provided.

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