Rarely needed: generation tools take an imageUrl directly. Use this only to import a photo into Pixly ahead of time, e.g. to reuse one URL across several tools without refetching it each time.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Publicly reachable image URL (JPG/PNG/WebP, max 10 MB) to import into Pixly |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a mutation (readOnlyHint: false). The description adds behavioral context by noting that importing avoids 'refetching' the URL each time, implying the image is stored/cached in Pixly. It does not contradict the annotations and adds value beyond the safety hints.
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 two sentences, front-loaded with the key point ('Rarely needed') and no redundant wording. Every phrase earns its place, providing purpose and usage guidance in a compact form.
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 with no output schema, the description covers purpose, usage context, and a hint of behavioral implications. It lacks explicit mention of the return value or post-import behavior, but given the low complexity and rich schema, it remains adequately complete.
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 documents the 'url' parameter with format, accepted types, max size, and reachability constraints (100% coverage). The description adds no additional parameter-level detail, so it relies on the schema—fitting the baseline of 3 for high schema coverage.
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 clearly states the tool's purpose: import a photo into Pixly ahead of time. It uses the specific verb 'import' and the resource 'photo into Pixly', and explicitly distinguishes itself from generation tools that accept an imageUrl directly, making it easy to understand when this tool is needed.
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?
The description opens with 'Rarely needed' and explicitly states when to use it (to reuse a URL across several tools without refetching) and when not to (generation tools already take an imageUrl directly). This provides clear, actionable guidance on tool selection relative to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action or resource: photo enhancement, decluttering, staging, day/night conversion, sign placement, video creation, uploads, job checking, credit balance, and library listing. Even related tools like cinematic_motion and before_after_reel have clear differences (single image vs. two frames). No genuine overlap exists.
Most tools follow a clear verb_noun pattern (declutter_photo, enhance_photo, get_job, list_library), but several use noun phrases (cinematic_motion, virtual_staging, before_after_reel, day_to_night). This mixed convention is still readable but not perfectly uniform.
With 13 tools, the server covers a wide range of real-estate media operations without being bloated. Each tool serves a specific need, and the count is well within the typical 3-15 range for a purpose-built server.
The tool surface covers the main workflows: photo enhancement, staging, editing, video creation, uploads, library viewing, job status, and credit management. Minor gaps exist like no delete/update for library items, but these are not critical for the core real-estate editing use case.
