match_job_to_profile

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the result is an analysis (scores, matched/missing skills, seniority fit), which is useful, but with an output schema present the return-content detail is largely redundant and no preconditions (e.g. stored profile requirement) are disclosed.

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 front-loaded sentence that leads with the action and then lists the outputs. Efficient, with no filler, though the enumerated outputs make it slightly list-heavy rather than prose-tight.

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 one-parameter read-only tool with an output schema, the description is adequate about what is produced, but it omits how to source job_id and any precondition that a stored profile must exist — gaps that matter given 0% parameter documentation.

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 0% and the single job_id parameter is undocumented in both schema and description. The phrase 'a posting' hints that an identifier is needed, but the description never explains what job_id is, its format, or where to obtain it (get_job/search_jobs), leaving the only parameter under-specified.

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 (compare) and both resources (posting, stored profile), then enumerates the analysis produced: score, matched/missing skills, seniority fit, relevant projects. This clearly separates it from siblings like get_job/get_profile, which merely fetch, though it does not name them explicitly.

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 only implied — the agent can infer 'use this to evaluate fit' — but there is no explicit when-to-use guidance, no prerequisites (e.g. a profile must be set first), and no named alternatives among the siblings.

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