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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on whether id or url is required, no indication that this is a live external lookup, and no behavioral context of its own.

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?

It is short and front-loaded, but the brevity is under-specification rather than economy; the single sentence conveys no information beyond the tool name. Nothing here earns its place because nothing is said.

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?

The output schema exists, so return values need not be described, but for a two-parameter lookup with 0% schema coverage and a dense sibling namespace, the definition omits the identifier format, the id-vs-url relationship, and any usage context. It is not complete enough for correct invocation.

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 two parameters (id, url), and the description does not compensate at all. The agent has no way to know whether 'id' expects an IMDb nconst (e.g. nm0000123), whether 'url' is a full profile URL, or how the two alternatives relate or which takes precedence.

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 'IMDb name details' is a noun phrase that essentially restates the tool name. It signals the resource (an IMDb person/name record) but supplies no verb or scope, so an agent cannot tell what 'details' means versus imdb_name_credits, imdb_name_awards, imdb_name_images, or imdb_name_videos.

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?

No when-to-use, when-not-to-use, or alternative routing is given. Sibling tools like imdb_name_credits and imdb_name_awards exist for sub-resources, and nothing here tells the agent to prefer this tool for the base profile versus those.

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