recommend

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, not what happens if profile is omitted (it is optional per the schema), not what an unrecognized profile yields, and not what the response contains. For a tool with zero annotation coverage, a single fragment is effectively no behavioral disclosure at all.

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?

There is zero wasted wording, but the content is a sentence fragment rather than a front-loaded statement of purpose, so the brevity comes at the cost of clarity. Conciseness here reads as under-specification rather than discipline.

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 and no annotations, the description is the only place an agent could learn what a "recommendation" returns, and it says nothing about the return value, the effect of omitting the optional profile, or how results relate to the ranking sibling. A single sentence is not sufficient for a tool whose entire contract is otherwise undocumented.

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 coverage is 100% and the schema itself enumerates "fast | cheap | capable" in the profile description, so the description adds no meaning beyond the structured field. With the schema doing all the work, the baseline of 3 is appropriate; notably the description also fails to explain what the optional/empty case means, which the schema leaves ambiguous.

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?

"Best model for a task profile" conveys the general idea of returning a model recommendation for a given profile, but it is a noun phrase with no verb and no indication of whether it returns one model, a ranked set, or a rationale. It also does nothing to distinguish itself from siblings like list_models or ranking, leaving the agent to guess which one produces a recommendation.

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 guidance on when to call this instead of list_models, ranking, probe, or report. The agent gets no signal about prerequisites, whether the call is deterministic, or when an alternative sibling is the better choice.

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