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 and delivers none. It says nothing about what the tool checks, what it returns, whether it mutates anything, or what the '30-day support promise' and 'prompt kit' framing even mean inside a tool call.

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?

It is brief, but the content is promotional filler rather than front-loaded functional information. Sentences about a support promise and 'no prompt engineering needed' consume the entire definition without earning their place.

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?

With no annotations, no output schema, and a vague one-parameter contract, the description needs to fully explain the tool's behavior and it does not. An agent has essentially no basis for deciding to call this rather than the neighboring dt-api-* tools.

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 100% on the single optional 'query' parameter, so the schema already defines its meaning as a scoping input. The description adds no additional semantics, but with full coverage the baseline of 3 applies.

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 never states what the tool actually does operationally. It restates the name in marketing terms ('api check tool workflow') and leads with unrelated branding ('AI-powered restaurant & brand intelligence pack'), leaving an agent unable to tell it apart from siblings such as dt-api-gen-tool or dt-api-tpl-tool.

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?

There is no guidance on when to use this tool, when not to, or which sibling to pick instead. The only imperative is a sales claim ('no prompt engineering needed'), which does not help tool selection at all.

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