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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds that scoring is 'deterministic', which usefully signals repeatable, reproducible ranking, but says nothing about result volume, cost, or how matches are ordered beyond that one adjective.

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 with no filler, which is appropriately terse. However, the brevity comes at the cost of substance rather than being earned conciseness, so it lands at the minimum-viable level rather than a 4 or 5.

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?

An output schema exists, so return values need not be documented, but a five-parameter search tool with two enums, zero schema descriptions, and no usage or scoping guidance is left substantially under-specified. An agent cannot know what 'surface' does or when to widen beyond the default 'buyer_job'.

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% and the description mentions none of the five parameters. The 'surface' enum (buyer_job, implementation_capability, research_evidence, all) and the 'product' enum (wave, quantum, robotics) are highly meaningful search controls that go entirely unexplained, and 'limit'/'schema_version' receive no elaboration either.

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 verb ('Select') and a resource ('Robotics buyer jobs'), so the general domain is clear, but 'work-language requests using deterministic semantic scoring' is opaque jargon that doesn't clarify whether this is a natural-language search, a ranking, or a filter. It never distinguishes itself from the sibling list_buyer_jobs or run_buyer_job, so an agent cannot tell which tool to reach for.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives such as list_buyer_jobs or run_buyer_job. The presence of a sibling that also enumerates buyer jobs makes this omission especially costly.

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