SeedreamMCP

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

No annotations provided, so description carries full disclosure burden. Adds valuable behavioral context by noting efficiency gains over single requests and specifying return value contents ('Status and image information'). However, lacks explicit safety disclosure (read-only nature), rate limits, or error handling behavior for invalid task IDs.

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?

Well-structured with clear information hierarchy: purpose statement, efficiency rationale, usage guidelines, and return value. Front-loaded with primary function. Bullet points for usage scenarios are efficient. Minor deduction for slight verbosity in 'Returns' section given that output schema exists.

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?

Adequate for a single-parameter tool with output schema. Covers invocation context (when to use), operational context (efficiency), and output context (status/image info). Could be improved by mentioning batch size limits or not-found behavior, but sufficient for agent selection and invocation.

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?

Input schema has 100% description coverage ('List of task IDs to query. Allows querying multiple tasks at once'). Description references 'task IDs' in context of batch efficiency but does not add semantic details (format constraints, max batch size, validation rules) beyond what the schema already provides. Baseline 3 appropriate 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?

Description uses specific verb 'Query' with resource 'Seedream image tasks' and scope 'multiple/at once'. Explicitly distinguishes from sibling 'seedream_get_task' by stating it is 'More efficient than calling seedream_get_task multiple times', clearly establishing the batch vs. single distinction.

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?

Provides explicit 'Use this when:' section with three concrete scenarios (multiple pending generations, several images at once, tracking a batch). Directly references the alternative single-task tool, giving clear guidance on tool selection.

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