Get Yorai model

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

readOnlyHint=true already declares the safety profile, so the description's burden is lighter. It adds real value by disclosing the contents of the response (generation types, limits, linkage rules, prices), which tells the agent what it can rely on after the call.

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 tight sentences with the payload description front-loaded and the call-ordering advice second. No filler; every clause carries information.

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 compensates by listing the fields the model record contains, which is what the agent needs to decide to call it. The remaining gap is the unexplained slug parameter, which keeps it from 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 0% and the sole parameter 'slug' is undocumented in both schema and description. The description only implies a model identifier via 'one model'; it never states what a slug looks like or where to obtain it (e.g., from yorai_list_models), leaving the agent to guess.

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 (get) and resource (one model) and enumerates exactly what comes back: generation types, input names/options/limits, linkage rules, and prices. The phrase 'one model' implicitly separates it from the sibling yorai_list_models, though the sibling is not named.

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?

Explicitly says to call it 'before quoting or creating a job,' which ties it to yorai_quote and yorai_create_job in the workflow. No when-not guidance, but the ordering rule is concrete and actionable.

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