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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value by bounding scope — contact details and CVs stay in the carbon.talent portal — which tells the agent what this call will NOT return. It says nothing about pagination or the cursor/limit behavior despite the tool being paginated.

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 tight sentences, front-loaded with what is listed and followed by the useful scope caveat. No filler, though the second sentence could be folded in more economically.

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 five undocumented parameters, no output schema, and a paginated result set, the definition leaves the agent without the input semantics it needs. The scope note is helpful but far short of complete for a tool of this shape.

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% across 5 parameters, so the description carries the full burden — yet it documents none of them. It never explains role_id, limit, stage filtering, cursor pagination, or include_rejected; 'stage' appears only as an output field, which is ambiguous against the input parameter of the same name.

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 (Lists) and resource (people who applied to / were added to one of your roles), plus the fields surfaced (stage, application date). It does not, however, distinguish itself from the sibling get_applicant_summary, which an agent must choose between.

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?

There is no statement of when to use this tool versus alternatives such as get_applicant_summary, search_talent, or get_role, and no prerequisites or exclusions are given. Usage is only implied by the phrase 'one of your roles'.

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