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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, authentication requirements, rate limits, data returned, or any other runtime behavior, leaving the agent completely in the dark.

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 only two words, which is not conciseness but severe under-specification. It fails to provide any meaningful content that would help an agent, and the minimal text does not earn its 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?

Given there is no output schema and no annotations, the description needed to explain the tool's purpose and behavior, but it does not. The description is completely inadequate for an agent to determine what to expect or how to invoke the tool correctly.

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?

The input schema provides a single required 'handle' parameter with a clear description 'Instagram handle', achieving 100% schema description coverage. The tool description adds no parameter-specific information, so the baseline of 3 applies as the schema does the heavy lifting.

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 'Embed HTML' merely restates the tool name in a human-readable form, providing no context about what the tool actually does. It lacks a specific verb+resource explanation and does not distinguish itself from the many similar scrapecreators_* tools.

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 absolutely no guidance on when to use this tool, what scenarios it is suited for, or how it differs from alternatives. There are no exclusions, alternatives, or usage context provided.

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