markovo_bundle_verify

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

No annotations provided, so the description carries full burden. 'Verify' implies a read-only check but the description doesn't disclose what verification entails, whether the bundle is downloaded first or supplied as a path/URL, what failure modes exist, or what the result means.

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?

One short, front-loaded sentence with zero waste. However, the brevity comes at the expense of the missing semantic detail rather than being efficiently informative.

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?

For a tool with no annotations, no output schema, and a 0%-documented parameter, the description is inadequate. It leaves the agent unsure what 'bundle' expects and what a verification result looks like.

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 coverage is 0% and the description adds no meaning for the single 'bundle' parameter. It's unclear whether bundle is a file path, URL, identifier, or binary content. The one parameter is undocumented in both schema and description.

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?

States a specific verb (verify) and resource (Markovo bundle), distinguishing it from siblings like markovo_convert or markovo_job_status. It's clear what the tool does, though it doesn't differentiate from a hypothetical verify-revoked-bundle variant among the named siblings.

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, nor any preconditions. The description gives no context about when verification is appropriate or what problem it solves in a workflow.

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