add_employee

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

Discloses default values for balance and history, which is helpful for understanding initialization. However, does not mention uniqueness constraints on employee_name or return behavior, and there are no annotations to rely on.

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?

Single, well-structured sentence that front-loads the action and resource. No unnecessary words 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?

Given the simplicity of the tool (1 param, output schema exists), the description covers essential aspects: action, defaults, and resource. Could be enhanced by mentioning return value or uniqueness, but adequate overall.

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 0% and the description adds no additional semantics for the lone parameter 'employee_name' beyond the schema's type declaration. For a tool with zero coverage, more detail (e.g., format, uniqueness) is needed.

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?

Clearly states the action 'add' and the resource 'employee', with specific defaults (balance 10, history []). Distinct from siblings which focus on leave operations.

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?

Usage is clear from context: this tool adds an employee while siblings handle leave-related actions. However, no explicit when-to-use or when-not-to-use guidance is provided.

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