Deduplicate job records

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, giving a safe operation profile. The description adds the key behavioral detail 'without contacting any provider,' which is not captured in annotations. This clarifies the tool is offline and purely transformational.

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 a single concise sentence with a clear action and key context. It is front-loaded and avoids redundancy. However, it may be too brief for the complexity of the deduplication/merge operation, leaving out important behavioral details.

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 complex operation involving normalization, merging, and deduplication, the description omits crucial context such as how duplicates are identified, what normalization entails, and what the return value looks like (no output schema). The tool's data model is rich (many fields), and the description does not address conflicts or edge cases. This is a significant gap.

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 input schema details the 'jobs' array with required fields, but the description does not explain these semantics. Schema description coverage is 0%, and the description only vaguely references 'supplied JobScout records' without describing structure, required fields, or validation rules. The description adds no value beyond the schema.

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 clearly states 'Normalize and merge supplied JobScout records' – a specific verb+resource combination that distinguishes this as a data transformation tool. It also adds 'without contacting any provider,' which separates it from sibling tools that search or list from sources.

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 phrase 'supplied JobScout records' implies it is used when records are already in hand rather than fetched via search. However, it does not explicitly state when to use this tool versus siblings like jobscout_search_jobs or jobscout_list_sources, nor does it provide exclusions or alternatives.

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