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 provided, the description carries the burden of behavioral disclosure. It explains the return behavior (presigned URL when ready) and reuse semantics. It does not mention timeout behavior or error conditions, but it does add useful context beyond the schema.

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 concise sentences, front-loaded with the primary action and outcome. There is no wasteful or redundant phrasing; both sentences contribute essential information.

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?

The output schema exists, so return values are covered elsewhere. However, the description does not mention how this tool fits with the sibling tool generate_upload_url or clarify the purpose of the filtering parameters (not_etag, modified_since). It also omits timeout behavior, leaving gaps for a complex polling tool.

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 already provides full descriptions for all four parameters, so the baseline is 3. The description adds meaning beyond the schema by explaining that session_id can be reused to poll for new uploads and that the capture URL can be reused, which enriches the semantics of that parameter.

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 polls an S3 bucket waiting for photo upload completion and returns a presigned download URL. It uses a specific verb ('poll') and resource ('S3 bucket'), and the stated purpose distinguishes it from the sibling tool 'generate_upload_url' which presumably creates the URL.

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 clear context for usage: after a session is established, the same session_id can be polled multiple times and the capture URL reused. However, it does not explicitly compare with the sibling tool or state when not to use this tool, so it falls short of a 5.

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