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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the behavioral fact that an empty query falls back to a newest-jobs listing, which is genuinely useful, but says nothing about pagination behavior, result caps, or freshness of the 'open jobs' data.

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?

Two short sentences with zero filler, and the core action is front-loaded ahead of the optional-parameter nuance. Nothing here needs to be cut.

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 paginated search tool with three undocumented parameters and no output schema, the description is thin but not misleading: it covers the primary action and the zero-argument case. It leaves the agent without guidance on pagination or result volume, which matters for a search endpoint.

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 description coverage is 0%, so the description must carry the burden for all three parameters, yet it only addresses 'query' (and only by omission behavior). The 'page' and 'limit' parameters, including their defaults and the limit maximum of 20, are left entirely unexplained in both the schema and the description.

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 gives a specific verb and resource ('Search open technology jobs'), so an agent knows exactly what the tool returns. It does not name or contrast the sibling retrieval tools (get_job, get_company, list_companies), but the search-vs-fetch distinction is reasonably self-evident.

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 supplies one useful usage rule: omitting the query lists the newest jobs, which tells the agent the parameter is optional and what the fallback behavior is. There is no guidance on when to prefer this over get_job or list_companies, and no note on typical search intent, so usage is implied rather than stated.

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