get_employee_summary

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

No annotations are provided, so the description carries the full burden. It transparently describes the return contents and implies a read-only database lookup via 'Get' and 'Returns.' However, it does not address potential permission requirements, data freshness, or any side effects; this is adequate for a simple summary getter but not especially rich.

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 extremely concise and front-loaded: two sentences, the first stating the main action and the second listing the returned data. Every sentence adds value and there is no redundancy.

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 zero-parameter read summary with an output schema present, the description covers the purpose and key return fields. It lacks explicit sibling differentiation and usage caveats, but given the low complexity and supporting output schema, it is reasonably complete.

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 tool accepts zero parameters, so there are no parameter semantics to clarify. The baseline of 4 applies because the schema has no parameter burden for the description to supplement.

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 uses the specific verb 'Get' with a clear resource: 'employee and company information from the database.' It enumerates exact return fields (name, fiscal code, hire date, role) and the number of payslips, which clearly distinguishes it from sibling tools focused on salary history, payslip details, or payslip search.

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?

There is no guidance about when to use this tool versus the sibling tools, no explicit alternatives, and no exclusions. The description is purely functional and does not help an agent decide between this and get_salary_history_tool, get_payslip_details_tool, or search_payslip_items.

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