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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description does disclose the concrete REST route and that each item carries an id and label, which is modest but real added context; it says nothing about pagination, ordering, or an empty-result case.

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 compact clauses with the purpose front-loaded and no filler. The trailing endpoint restatement ('GET /v1/parser/models/{parser_id}') is mildly redundant with the description body and the readOnly annotation, costing it the top mark.

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?

A single-parameter, read-only list tool with no output schema, and the description compensates by naming the returned shape (id and label) plus the endpoint. For this complexity level that is sufficient, though pagination behavior for the list remains unstated.

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?

Only one parameter with 100% schema description coverage, so the schema fully documents parser_id, including its pattern and its origin from docparser_list_parsers. The description adds no syntax or format meaning beyond the {parser_id} path placeholder, matching the baseline for high-coverage schemas.

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?

Specific verb (List) plus a precisely bounded resource (model layouts of one parser), and it even names the returned fields (id, label). This clearly separates it from docparser_list_parsers, which enumerates parsers rather than one parser's models.

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?

Usage is only implied: the '(one parser)' scoping and the parser_id path parameter signal that a parser context must already exist. There is no explicit when-to-use, when-not-to-use, or named alternative among the siblings.

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