mdl_titles_get_title

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description contributes nothing on top of that — no statement about what is returned, what happens on a missing/invalid id, or whether the id is a TMDB-style integer or a slug, despite the schema allowing both.

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?

Five words with no padding, but this is under-specification rather than conciseness; there is no front-loaded detail because there is no detail to front-load.

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, no annotation gaps it can fill, and a required polymorphic id parameter, the description would need to carry real weight — and it carries none. Nothing tells the agent how to identify a title or what it will receive back.

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% for the single required parameter title_id, and the description does not compensate at all — it never mentions the id, its dual integer-or-string form, or its pattern constraint. The schema's anyOf types are the only signal the agent has.

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?

"Titles: get title" is essentially a restatement of the tool name mdl_titles_get_title; it names a verb and resource but adds no scope, no return-shape hint, and no distinction from siblings like mdl_titles_get_reviews or mdl_titles_get_credits that also fetch a title's facets.

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 at all about when to use this tool versus the many sibling title endpoints, no prerequisites, and no exclusions. An agent gets nothing to route on beyond the name itself.

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