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

Annotations already cover the read-only, non-destructive, open-world profile. The description adds real context beyond that: only active employees are returned, services are bounded by the limitations configured in DaySmart, and an API key with app access is required. It stops short of describing pagination or return shape.

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?

Front-loaded with the resource and scope, and short overall. Mild redundancy between 'Active employees with...' and 'Returns active employees,' which could be merged, but nothing is bloated.

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 parameterless read-only list tool with no output schema, the description covers what comes back, the active-only filtering, the service-limitation caveat, and the auth requirement. An agent has enough to call it correctly; only return-format detail is absent, which is acceptable without an output schema.

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?

There are zero input parameters, so the schema has nothing to document and the baseline is 4. The mention of employee_id refers to parameters of other tools, not this one, so it adds no parameter meaning here.

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?

States a specific verb (list) and resource (employees), plus the scope ('active employees') and what accompanies them ('the services they can perform'). It is unambiguous on its own, though it never names a sibling tool to distinguish itself from the DaySmart client- and appointment-oriented tools.

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?

Provides explicit downstream usage: 'Use employee_id with list_appointments and book_appointment,' which tells the agent why to fetch this data. It does not, however, give any when-not-to-use or alternative-tool guidance.

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