Remote Camera

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

With no annotations, the description carries the behavioral burden. It discloses reusability and the exact URL format, which is helpful. However, it does not mention any potential side effects, expiration, rate limits, or whether this creates a persistent record. For a generation tool with no annotations, this is adequate but not rich.

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?

Three concise sentences, each adding meaningful information. The description is front-loaded with the core action and includes practical format details without any fluff.

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 single-parameter tool with an output schema, the description covers purpose, usage, reuse, and output format. It doesn't explicitly link to the sibling polling tool, so there is a small gap in the overall workflow, but the tool itself is well described.

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 schema description covers the 'message' parameter fully (instructions to display, max length), so the description adds only marginal value by implying the message is shown on the capture page. Baseline of 3 is appropriate given 100% schema coverage and no additional parameter details in the description.

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 verb 'Generate' and the resource 'URL for remote camera upload', and explains its purpose (sending to a mobile device for photo capture). It also explicitly distinguishes from the sibling tool 'poll_for_upload' by focusing on generation rather than polling.

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 provides concrete usage context ('Send this URL to a mobile device to capture and upload a photo') and notes that the URL can be reused. It doesn't explicitly mention poll_for_upload as an alternative or next step, so it stops short of full exclusions, but the context is clear.

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

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool blocks while waiting, returns a presigned download URL, and that polling is repeatable with the same session_id so the capture URL can be reused. It does not describe timeout failure behavior, but the blocking nature is implied and the reuse property is a valuable behavioral disclosure.

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?

Two sentences with no filler. The first sentence states the core action and result, and the second adds a key reuse behavior. Every clause contributes useful information, and the most important details are front-loaded.

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?

Given the output schema and complete parameter schema, the description provides sufficient context for most calling scenarios: it defines the polling purpose, the return value, and the reuse capability. It could be more explicit about timeout behavior or the prerequisite of generating an upload URL, but these are inferable from the parameter schema and sibling tool name.

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. The description adds meaning beyond the schema by explaining that session_id can be reused across multiple polling calls and that this allows the capture URL to be reused, which is not stated in the session_id property description. Other parameters are already well documented in the schema.

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 states a specific verb, resource, and outcome: 'Poll S3 bucket waiting for photo upload to complete' and 'Returns a presigned download URL when the file is ready.' This clearly distinguishes it from the sibling generate_upload_url, which creates the upload URL rather than waiting for completion.

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?

It provides clear context for when to use the tool: after an upload has been initiated, to wait until it completes and obtain a download URL. It also gives a usage pattern by stating the same session_id can be reused for multiple polls, but it does not explicitly contrast with generate_upload_url or state when not to use this tool.

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