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

Annotations already declare readOnly, idempotent, and non-destructive, so the description rightly doesn't repeat those. It does add a genuinely useful operational fact beyond the structured fields: the call requires the user's personal access token, an auth requirement the schema does not express.

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?

Three short sentences, front-loaded with the payload contents and ending with the auth constraint. Slight awkwardness in 'the seniority, workplace and places they want' keeps it from being maximally clean, but there is no filler.

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 an output schema documenting return values, no parameters, and annotations covering the safety profile, the description only needs to add purpose, consumers, and auth — and it does all three. Only the relationship to update_preferences is left implicit.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing parameter-wise the description needs to compensate for.

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?

The description enumerates exactly what the tool returns (skills, seniority, workplace, places, alert email timing), which is more specific than the title alone. It doesn't use an explicit verb like 'retrieve' and doesn't name update_preferences as its write counterpart, so the read/write split is only implied by context.

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?

It states who consumes the preferences ('the board's best matches and the account overview use them'), which hints at when an agent would want this data. There is no explicit when-to-use/when-not guidance and no mention of the sibling update_preferences for the mutation case.

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