workflowmoves_wordpress_inventory

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

Beyond the annotations (which only flag non-read-only, open-world, non-idempotent, non-destructive), the description discloses that the call returns a retained background job rather than a result, that credentials are operator-bound, and that write/network effects apply at base with conditional inference/download effects. The async-job semantics are the most valuable addition since no annotation expresses them.

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 short sentences, front-loaded and free of padding, so it is efficiently sized. But the density of internal vocabulary ('canonical guarded transport', 'retained background job', 'base effect flags') trades brevity for opacity rather than clarity.

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?

An output schema exists, so return values need not be explained, and the description covers the async handoff well. For a write-capable, nested-parameter tool with 50% schema coverage, though, it omits what the inventory actually contains, what the receipt output is for, and how the conditional inference/download permissions are triggered.

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 50%: the 'permissions' object is self-documented, but 'receipt_out' has no description. The description's 'new receipt' phrase and the enumerated base effect flags (write, network) map onto these parameters and add some meaning, but they do not explain what a receipt is, why receipt_out cannot begin with a dash character, or when to set each permission flag.

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 verb is concrete ('Invoke') and the resource is named ('canonical guarded WordPress transport'), but the actual operation — producing a WordPress inventory — is never stated. 'Transport' is internal jargon, and an agent must infer from the tool name alone what inventory of what WordPress entities is being collected.

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?

It gives useful post-invocation routing: 'poll danceflow_job_status' and 'Inspect danceflow_component for conditional inference/download effects'. However, it never says when to use this instead of the neighboring workflowmoves_wordpress_read_post, upload_media, create_draft, or publish_post tools, nor what preconditions (credentials, permissions acknowledgements) must hold before calling.

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