list_employees

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

Annotations already mark read-only. Description adds that it returns raw employee list payload and advises on per_page size. Could mention more about pagination behavior or limits.

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?

Well-structured with Args list and usage note. Slightly verbose with 7 sentences; could be trimmed without losing value.

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?

Covers all 4 parameters, use case, and return type. No output schema but description helps. Could mention other potential filters (e.g., department) but sufficient for common use.

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 has no descriptions (0% coverage). Description fully explains each parameter: status meaning, page_number zero-based, per_page range suggestion, order options.

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 it lists employees in the organization and returns raw payload. Distinguishes from sibling 'get_employee' by mentioning ID resolution for other 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?

Explicitly states when to use: to resolve employee name to ID before calling other tools. Implies when not to use (not for single employee). Excellent guidance.

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