bamboohr_add_employee

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

The description discloses no behavioral traits such as side effects, required permissions, rate limits, or consequences of the operation. With no annotations provided, the description fails to inform the agent about what happens during execution.

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 short (3 sentences) but wastes a sentence on routing details ('Routes through /api/tools/invoke...') that may not aid tool selection. It is not well front-loaded; the first sentence is the least informative. Still, it avoids verbosity.

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 that the tool has an output schema and 0% schema coverage, the description is severely incomplete. It does not explain what fields are required in arguments, what the operation does in detail, or what the response contains. For an 'add employee' operation, this is grossly insufficient.

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 only parameter 'arguments' is described as 'JSON string of arguments for the connector operation', which adds minimal meaning beyond the schema type. With 0% schema description coverage, the description should compensate by detailing expected JSON structure, but it does not.

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 merely restates the tool name as a 'connector operation add_employee' without explaining what adding an employee entails or what specific employee data is created. It lacks a clear verb-resource statement, making it only slightly more informative than a tautology.

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?

No guidance is provided on when to use this tool, what prerequisites are needed, or how it differs from alternatives. There is no mention of use cases, limitations, or comparisons to sibling tools.

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