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

The readOnlyHint annotation already tells the agent this is a safe read. The description adds useful context beyond that: it identifies the underlying endpoint (GET /info) and the shape of the returned metadata, which matters because there is no output schema. It does not explain how the optional context parameters (model_id, dev_mode, age) affect the response.

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, with the purpose and the returned fields front-loaded. The trailing 'Engine API: GET /info.' is arguably redundant but cheap and useful for endpoint-oriented users.

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?

For a simple read-only metadata tool this is largely complete: it says what comes back and which endpoint is hit, compensating for the absent output schema, and the optional parameters are fully covered by the schema. Only the absence of when-to-use guidance keeps it short of a 5.

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 all three optional parameters are already documented with their header mappings and defaults. The description adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 metadata about the current Infermedica medical model') and enumerates the payload (version, last update, concept counts). It is clearly distinct from the get_*/list_* concept siblings, though it never names an alternative the way a 5 would.

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 statement of when to call this versus the sibling metadata/entity tools, nor any prerequisites or exclusions. Usage is only implied by the word 'current' and the fact that it describes a model-level resource.

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