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

Beyond readOnlyHint=true, it discloses a rate limit (100 requests per minute), warns that the full record exposes sensitive HR data like compensation and addresses, and explains the pagination termination signal. These are precisely the behavioral facts annotations cannot carry.

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?

Purpose is front-loaded in the first clause, followed by return shape, format choice, pagination, and API/rate-limit details. Every sentence carries information, though the single dense paragraph could be split for scanability.

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?

With no output schema, the description still supplies return shape ({profiles, meta:{count}, linked}) and pagination semantics. An agent has everything needed to call and iterate correctly.

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 100%, so baseline is 3, but the description adds meaning by spelling out what format=short returns (ids, names, email, status, job title) and that full includes every visible custom field. Other parameters such as reports_to and the exact-match filters are left to the schema.

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?

Specific verb+resource (list employee profiles) with scope stated: includes active, pending and inactive unless filtered. It is clearly distinguishable from the sibling namely_get_profile, which fetches a single profile.

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?

Gives concrete selection guidance: use format=short for a smaller record versus full for all custom fields, and notes an empty page means the end of pagination. It never explicitly names when to prefer namely_get_profile or how to combine filters, so it stops short of full alternative routing.

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