toast_get_employee

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'Get detailed information' without addressing response format, error handling, authentication, or any side effects. The read-only nature is implied but not stated explicitly.

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, which is appropriate in length, but it's under-specified rather than genuinely concise. It provides minimal value and lacks essential details, making it only marginally better than a tautology.

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 no annotations, no output schema, empty parameter descriptions, and 53 sibling tools, this description is severely incomplete. An agent would not know how to differentiate this from list/search tools or how to properly populate the parameters, leading to likely misuse.

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 0% — the parameter descriptions are empty. The description adds no meaning to employeeGuid or restaurantGuid, failing to explain that employeeGuid is required and restaurantGuid is optional or what each is used for.

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 it retrieves detailed information about a single employee, which distinguishes it from list/search siblings by implying it fetches one record. However, it doesn't explicitly mention the use of employeeGuid as the identifier, so it's clear but not fully precise.

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 versus toast_list_employees or toast_search_employees. It doesn't state that this should be used when you have a specific employee GUID, nor does it mention any prerequisites or alternatives.

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