Model Get Tool

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuine context with 'allowlisted' and 'allowlist projection', signalling that only a restricted set of models is queryable and that returned fields are filtered. It does not say what happens for a non-allowlisted model, nor what the projection omits.

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?

A single front-loaded sentence with no filler, and the key constraint (one record, by id) comes first. The jargon 'allowlist projection' is dense and slightly opaque, but nothing 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?

For a simple two-parameter read tool with annotations covering safety, the description is close to adequate. It still leaves the agent guessing about valid model values and the meaning of the projection, which matters because the schema documents nothing.

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 carry both parameters. It only hints that id is a record identifier; the model parameter has no explanation of accepted values, format, or how to discover valid names (no enum exists in the schema). The term 'allowlist' is introduced but never defined.

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 states a specific verb and resource: fetch one Evolution CMS model record by id, with results filtered through an allowlist projection. It implicitly contrasts with the sibling list tool by specifying 'one' record 'by id', though it never names evo.model.list as the alternative.

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: 'by id' tells the agent this is a single-record lookup rather than a search or list. There is no explicit statement of when to prefer it over evo.model.list or evo.elements.get, and no mention of prerequisites such as needing a valid allowlisted model name.

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