Generate a bear placeholder image URL with custom width and height and no network call. Set pixel dimensions up to 2000 for mockups, layouts, or testing.
Get a bear placeholder image URL at custom dimensions (no network call).
| Name | Required | Description | Default |
|---|---|---|---|
| width | No | Image width in pixels (default 300, max 2000). | |
| height | No | Image height in pixels (default 300, max 2000). |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description only needs to add something new. It does contribute the useful detail that no network call is made, telling the agent the operation is local and deterministic — though this sits in mild tension with openWorldHint=true, and it doesn't clarify that the result is a URL string rather than image bytes beyond the tool name.
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?
A single front-loaded sentence with zero filler; the key behavioral caveat ('no network call') is included without padding.
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 two-optional-parameter read-only helper with full schema coverage and no output schema, the description covers purpose, dimension configurability, and the local-execution behavior. Only a hint about the returned URL shape or how dimensions are reflected would improve it.
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 100%, with width and height already documented including defaults (300) and max (2000). The description only restates 'custom dimensions' and adds no format, unit, or clamping behavior beyond the schema, so the baseline 3 is appropriate.
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 and resource ('Get a bear placeholder image URL') plus the customizable dimension, so the agent knows exactly what it produces. It does not differentiate itself from nearby siblings such as placekitten_image, placeholder_image, or dummy_image_url, which would require a quick scan to distinguish.
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?
Gives no explicit when-to-use or when-not-to-use guidance and never names an alternative. The parenthetical '(no network call)' implies cheap, side-effect-free usage but is not framed as a selection rule, leaving the agent to infer why it would pick this over the other placeholder-image tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.