runsync-endpoint

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

Discloses max payload 20 MB, result expiration after 1 minute, wait parameter behavior, and webhook option. No annotations, so description carries full burden and meets it well.

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?

Concise 4-sentence description with front-loaded purpose. Every sentence adds unique value without redundancy.

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 input, behavior, alternatives, and timeouts. Lacks output format details but mentions return of job ID. Reasonably complete for a synchronous 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?

Schema already covers all parameters with descriptions (100% coverage). Description adds context: max payload, result expiry, and best-use scenario, enhancing understanding beyond 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?

Description clearly states 'Submit a synchronous job to a Serverless endpoint and wait for the result,' specifying the action (submit synchronous) and resource. It differentiates from siblings by noting the synchronous nature and fallback polling behavior.

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?

Explicitly indicates best for tasks within 90 seconds, with fallback polling via get-job-status if exceeded. Also mentions extending wait up to 5 minutes and using webhook as alternative.

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