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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint/openWorldHint false, so the safety profile is covered. The description adds that the result set is a fixed 20-job portfolio (implying no filtering or pagination), which is useful, but it says nothing about the return shape or what 'readiness' means operationally.

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 structurally efficient. The density of unexplained jargon ('agent discovery contracts') works against readability but doesn't waste words.

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-value detail is not required, and annotations cover safety. However, given three undocumented enum parameters and a closely-related sibling (search_buyer_jobs), the description is too thin to disambiguate the tool or its inputs.

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 never mentions the three parameters at all, so it does not compensate. The fixed 'Robotics' phrasing actually conflicts with the product enum (wave/quantum/robotics) and the surface enum, leaving the agent to guess how product/surface/schema_version map to the described behavior.

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 verb "Return" and the resource "20-job RQM Robotics portfolio" give a rough sense of what the tool does, but the phrasing "complete agent discovery contracts and readiness" is opaque jargon that doesn't translate into a clear action. It also fails to differentiate from the sibling search_buyer_jobs, which is the obvious near-identical alternative.

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 mention of when to prefer search_buyer_jobs over this tool. The only inference an agent can make is from the fixed '20-job' scope, which is indirect at best.

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