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

Annotations already declare the tool as read-only, non-destructive, and idempotent; the description adds that the output is prose, only preference-language observations, and that no external actions occur. This goes beyond the annotations and clearly sets behavioral expectations for an agent.

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?

The description is two sentences with no filler. The core purpose is front-loaded in the first sentence, and the second sentence crisply defines output constraints.

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?

Given that an output schema exists and annotations cover the safety profile, the description sufficiently explains what the tool does, what it returns, and what it avoids. Missing explicit sibling routing and any hint about tenant_id are minor gaps for a read-only explainer.

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 schema already describes queue_item_id and owner_preferences well, and the description maps to these concepts (existing saved job and owner preferences) without adding further meaning. The optional tenant_id remains undocumented in both the schema and description, so the description does not compensate for that coverage gap.

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 states a specific verb ('Explain'), a concrete resource ('existing saved job'), a comparison target ('account owner's stated workplace preferences'), and an output form ('in prose'). It further differentiates itself from scoring/decision siblings by explicitly excluding numbers, rankings, recommendations, decisions, and external actions.

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 description provides clear context: the tool is for explaining overlaps/differences for a job already in the queue versus owner preferences. It also signals when not to use it by stating it produces no numbers, rankings, recommendations, or decisions, implying it is not the scoring tool. However, it does not explicitly name sibling alternatives like talent_scout_score_fit.

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