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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds useful scoping context (pay figures are 'advertised now', legitimacy is a 'researched review', ratings only 'where one exists'), but says nothing about behavior for unknown platforms or data freshness beyond the word 'now'.

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 that leads with the core resource and then enumerates return contents, with no filler or marketing fluff. The heavy nested parentheticals make it dense and slightly hard to scan, which keeps it below a 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?

One required parameter, no output schema, and the description effectively serves as the return-value contract by listing roles/pay, legitimacy, acceptance, fit and page link. What remains unstated is the failure mode for an unknown platform and whether pay data is live or cached, but the definition is otherwise sufficient to call correctly.

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?

With a single parameter and 100% schema description coverage, the schema already documents the 'platform' field including examples and the name-or-slug flexibility. The description corroborates by listing real platform names, but adds no format or matching rules (e.g., whether matching is case-insensitive) beyond the schema, so baseline 3 applies.

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?

Names a specific resource (a single AI training platform profile) and enumerates what the response covers: open roles and advertised pay, legitimacy review with risk and payment details, acceptance requirements, fit, and a link. It is clear what the tool returns, but it never contrasts itself with siblings such as get_ai_training_pay or get_ai_training_market, so the overlap with pay-focused siblings is left for the agent to resolve.

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 'One AI training platform' implicitly signals single-platform lookup versus the market/pay siblings, and 'for example Mercor, Outlier...' hints at accepted inputs. However, there is no explicit when-to-use, no exclusions, and no named alternative such as 'for cross-platform pay comparisons use get_ai_training_pay'; usage must be inferred from sibling names alone.

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