ExecuteAdhocWorkflowInstance

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('执行临时工作流实例') without any information about permissions required, whether it's a read or write operation, what happens upon execution (e.g., does it trigger immediate runs, create instances, or modify state?), error handling, or rate limits. For a complex execution tool with 6 parameters and no annotations, this is a significant gap in transparency.

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 concise with a single sentence in Chinese, but it's under-specified rather than efficiently informative. The second sentence about the 'MCP Resource' adds clutter without clarifying the tool's purpose or usage—it's meta-commentary about examples rather than helpful description. While brief, it fails to front-load critical information and includes a sentence that doesn't earn its place in the core description.

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 tool's complexity (6 parameters with nested objects, no output schema, and no annotations), the description is incomplete. It doesn't address what the tool returns, how errors are handled, or the implications of executing an 'adhoc' workflow (e.g., is it ephemeral, does it persist results?). The description lacks context about workflow systems, making it inadequate for an agent to understand the full scope of this execution 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 description coverage is 100%, meaning all parameters are documented in the input schema with descriptions. The tool description adds no parameter information beyond what's in the schema—it doesn't explain relationships between parameters (e.g., how Tasks array relates to Name and Owner), provide examples, or clarify semantics like what '临时' (adhoc) means for parameter values. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 '执行临时工作流实例' (Execute ad-hoc workflow instance) provides a basic verb+resource combination, indicating it runs workflow instances. However, it's vague about what constitutes an 'ad-hoc' workflow versus regular workflows, and doesn't distinguish this tool from sibling tools like 'CreateWorkflowInstances' or 'StartWorkflowInstances' that also handle workflow execution. The purpose is understandable but lacks specificity.

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 offers no guidance on when to use this tool versus alternatives. There are multiple sibling tools related to workflow execution (e.g., 'CreateWorkflowInstances', 'StartWorkflowInstances', 'StopWorkflowInstances'), but the description doesn't explain when 'adhoc' execution is appropriate or what differentiates it from other workflow tools. Usage is implied only by the name 'Adhoc', but no explicit context or exclusions are provided.

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