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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding ordering ('most recent first'), return content ('AyHire's call and the notes'), and parity with the web app view. It does not mention result limits or pagination, which is the main remaining behavioral gap.

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?

A single sentence with the resource and scope front-loaded, qualifiers in parentheses, and zero filler. Nothing could be cut without losing meaning.

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 read-only, zero-required-parameter listing tool with no output schema, this is nearly complete: it says who is returned, the ordering, and the key fields included. The only omission is whether results are paginated or capped.

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?

Only one parameter and schema coverage is 100%, so the schema already documents the workspace name/id, the optional default, and the list_workspaces cross-reference. The description reinforces the default ('your current workspace') but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource (everyone shortlisted), the scope (current workspace or a named one, across its roles), and anchors it to a known artifact ('the same list as the web app's Shortlist'). That anchor plus the ordering and content details ('most recent first, with AyHire's call and the notes') clearly separates it from search_candidates and find_people_for_role.

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?

Usage is implied rather than stated: the description tells the agent this is the web app's Shortlist view scoped to a workspace, and the schema points to list_workspaces. It never says when to use this versus search_candidates or find_people_for_role, and no exclusions or prerequisites are given.

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