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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely new behavioral context the annotations do not: the required employees.read scope and the zero-based pagination convention, both of which affect whether a call succeeds and how to iterate.

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?

Two short sentences, front-loaded with purpose and permission, no filler. The 'limit max100' clause is redundant with the schema's maximum, which is the only wasted element.

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?

There is no output schema, so the description should say something about what a page of employees contains or how to detect the last page. It covers auth and pagination basics but leaves the return shape and end-of-list behavior entirely undocumented for a list tool.

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%, so the description carries the burden for both params. It supplies the important non-obvious fact that pagination is zero-based, but 'limit max100' merely restates the schema's maximum:100, and neither param's effect on results (e.g., what a page contains, defaults) is explained beyond that.

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 and resource ('Read employees'), which cleanly separates it from the singular builderprime_get_employee sibling. It does not explicitly name that sibling or describe the scope of the list, but the list-vs-get distinction is clear enough to select correctly.

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?

The permission note ('requires employees.read') implies this is the collection-level read path, but the description never says when to use this versus builderprime_get_employee for a single record, nor any filtering or exclusion guidance. Usage is inferable from the name only.

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