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

Annotations already declare readOnlyHint=true, but the description usefully adds that this is a non-mutating POST operation, which prevents an agent from mistaking POST /triage for a write. It also names the returned triage levels and observations, though it omits auth, error, or rate-limit behavior.

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?

Three concise sentences, front-loaded with the main action and output categories, then the non-mutating clarification and API endpoint. No sentence is wasted.

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?

With no output schema, the description appropriately names the return categories: triage level and serious/emergency observations. The nested input schema covers parameter details, but the description could do slightly more to explain required inputs or evidence expectations.

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 high at 83%, so the baseline is 3. The description only mentions 'given the evidence' and does not add syntax or format guidance beyond what the schema already provides for sex, age, evidence, extras, dev_mode, and model_id.

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 specific verb and resource: recommend a triage level, with the full set of possible triage outputs enumerated. This clearly separates it from diagnosis or explanation siblings by output type, though it does not explicitly name an alternative tool.

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 'given the evidence' implies the tool should be used after evidence is collected, and 'Non-mutating computation' clarifies the operation type. However, there are no explicit when-to-use/when-not-to-use rules and no named alternatives such as infermedica_diagnosis.

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