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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no additional behavioral traits beyond the read-only nature of the search. It is consistent with annotations but does not provide further insight (e.g., rate limits, authentication needs).

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 concise (three short sentences) with no redundant information. All content is relevant: scope, filters, return values, and use case. It is front-loaded and easy to parse.

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 the tool's complexity (6 parameters, rich annotations, output schema), the description adequately covers the main aspects. It might lack explicit mention of pagination or limit behavior, but the schema covers that. It is sufficiently complete for an AI agent to understand when and how to use the tool.

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 has 100% description coverage, so parameters are well-documented. The description summarizes the filters and return fields but adds only marginal value by listing output fields (though an output schema exists, reducing the need). Overall, it does not significantly augment 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 the tool's purpose: searching 181M+ job postings with specific filters (keywords, country, remote, tech stack, recency) and lists return fields. It distinguishes itself from sibling tools by specifying the data source (TheirStack) and use case (job market intelligence, hiring analysis).

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 implies the tool is for job market intelligence and talent sourcing, providing context for use. However, it does not explicitly state when to use this tool over alternatives like jobs.adzuna.search or jobs.jooble.search, nor does it mention exclusions or prerequisites.

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