ddg_order_artifact

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

With no annotations, description must carry behavioral burden. It implies readiness check ('when ready') but fails to disclose caching, blocking, polling, error handling, or what happens if artifact is not ready.

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?

Single sentence with no redundancy, but overly terse – could be expanded with minimal structure to cover key details without becoming verbose.

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?

Despite having output schema, description lacks guidance on when to call vs siblings, what triggers 'ready', and parameter interaction; insufficient for a two-parameter tool with no annotations.

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 0%; description only hints at 'agent-scoped' for agent_id and 'order artifact' for order_id, without explaining constraints, formats, or the role of optional agent_id.

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 uses a specific verb 'Fetch' and resource 'DDG order artifact', with qualifiers 'agent-scoped' and 'when ready', clearly distinguishing it from sibling tools like ddg_order_status or ddg_submit_order.

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?

No guidance on when to use this tool versus alternatives, such as ddg_order_status for order state or ddg_submit_order for creation. Absence of any usage context or exclusions.

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