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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds valuable endpoint-specific behavioral context: api_key is optional on the public endpoint but a missing key is refused on /mcp/mcp. It also states the output format choices and the synthetic nature of the artifact, which is beyond what the annotations or schema alone provide.

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 compact and front-loaded: the first line states the core purpose and artifact contents, the second covers output formats in a direct way, and the third covers api_key behavior. The phrase 'Layer 7' is unexplained jargon and is the only notable inefficiency; otherwise, every sentence earns its place.

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 schema, annotations, and output schema, the description covers the major operational points: artifact content, format choice, and auth. The main gap is why an agent would prefer this over per-ranking or per-agreement sibling tools, and there is no guidance on how ranking_id should be obtained. Still, for invocation-focused needs it is enough.

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 compensate for all parameters. subject, however, it only explains formatting_messages: format defaults to markdown and json is available for a structured summary; api_key is optional on the public endpoint but refused on /mcp/mcp. It says nothing about ranking_id beyond its property key, so an agent must still infer the provenance and format of that identifier.

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 a specific verb and resource: it produces an automatic data card containing provenance, IAA, coverage, per-annotator quality, and agreement stats as a markdown audit artifact. This is more specific than many get_* siblings, though it does not explicitly contrast the tool with any sibling, so differentiation is conveyed mainly by content rather than direct comparison.

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 gives limited operational guidance: the format options and the api_key endpoint behavior. It does not state when to choose this over alternatives like aimrank_get_ranking or aimrank_get_matches, nor does it provide exclusions or alternative-selection criteria. The intended usage must be inferred from the purpose sentence.

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