get-portrait-image

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

With no annotations provided, the description carries the full burden. It only lists the returned items ('image URL' and 'links') but does not disclose any behavioral traits such as read-only status, potential errors, rate limits, or whether the URL is temporary or direct. No safety or side-effect information is given.

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?

The description is a single clear sentence with no filler. It front-loads the primary action and outputs, and every word earns its place.

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 one-parameter tool, the description states the return types ('image URL' and 'web page links'), but lacks detail on the response structure (e.g., whether it is a single URL or an object with multiple links), error conditions, or any additional fields. No output schema exists, so the description is expected to cover return semantics more fully. This is adequate but leaves ambiguity.

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?

The input schema already describes portraitId fully with an example. The description's phrase 'by its identifier' adds little beyond the schema. Since schema coverage is 100%, the baseline of 3 is appropriate; the description does not contribute significant extra parameter meaning.

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 uses a specific verb 'Get' and names the exact outputs ('direct high-resolution image URL (JPEG) and web page links') and input ('by its identifier'). This clearly distinguishes it from sibling tools like search-portraits and get-portrait-details, even without naming them.

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 guidance is given on when to use this tool versus alternatives. It does not state prerequisites (e.g., 'use after search-portraits to obtain an identifier') or explain when to prefer get-portrait-details instead. The intended usage is only implicit through the phrase 'by its identifier'.

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