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

The readOnlyHint annotation already declares this a safe read, and the description adds the concrete endpoint (GET /conditions/{id}), reinforcing it. It omits any auth, rate-limit, or 404/error behavior, so value beyond annotations is modest.

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 short sentences, zero waste, with the core operation front-loaded and the endpoint mapping as secondary support. Nothing needs trimming.

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 simple single-entity read tool with full schema coverage and a readOnlyHint; the description plus annotations are enough to call it correctly. The only minor gap is that no output schema exists and the description doesn't hint at the returned condition shape, though that is not essential for invocation.

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 100%, so id, age, dev_mode, and model_id are all documented in the schema itself. The description only reiterates the id lookup and adds nothing about the optional age context or header-mapping parameters, 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?

States a specific verb and resource ('Get a single condition by its id') plus the underlying endpoint, which cleanly separates it from sibling list_conditions. It stops short of naming the sibling or contrasting scopes, so it's clear but not maximally differentiated.

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 explicit when-to-use, when-not-to-use, or alternative routing. The agent must infer from 'single condition by id' that this is the lookup path versus infermedica_list_conditions or infermedica_search_concepts, with no supporting guidance.

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