Create photo upload link

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

Annotations only declare read-only=false/openWorld=false/destructive=false; the description adds substantial context beyond them: no login required, 24-hour expiry, that a property is created when propertyId is omitted, that type '360' causes non-360 uploads to be refused, and that 360° photos are auto-recognised.

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?

Front-loaded with the core purpose and validity constraint, then routing and follow-up steps. Dense with useful information, though the trailing parenthetical about the local server is somewhat long and could be tighter.

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?

Covers purpose, access model, expiry, side effects, parameter behaviour, the downstream workflow, and the local-server alternative. With no output schema and full schema coverage, nothing essential for correct invocation is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real semantics: propertyId omission triggers property creation, and type '360' enforces refusal of other content. It slightly restates the schema's own type/name descriptions, keeping it from a 5.

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 link where the user... uploads photos... into a property') with clear scope: no login, 24-hour validity. It is readily distinguishable from siblings like pedra_add_images_to_property and pedra_add_local_panoramas, which are named in the routing text.

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?

Explicit when-to-use: 'whenever the photos are files on the user's device that weren't attached to the chat.' It also names the alternative path for local files (passing a local imageUrl or using pedra_add_local_panoramas), and states the follow-up sequence (wait, then pedra_list_property_images or pedra_create_virtual_tour).

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