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, but 'Highlights Details' reveals nothing about side effects, output format, required permissions, or whether this is a read-only operation. It fails to describe the behavior entirely.

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?

Two words is underspecified, not appropriately concise. The phrase provides no actionable information and is not front-loaded with useful content. It reads as a label rather than a tool description.

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 the lack of annotations, output schema, and description content, this is completely inadequate. The tool may be simple (one ID parameter), but the description still needs to explain what 'details' means or what kind of data is returned, which it does not.

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 has one parameter `id` with a clear description: 'The ID of the highlight to get details for'. With 100% schema coverage, the baseline is 3, and the description adds no additional semantic value beyond what the schema already states.

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 'Highlights Details' is a noun phrase that essentially restates the tool name 'scrapecreators_highlights_details'. It lacks a verb or explicit action, making it a tautology rather than a clear statement of purpose.

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 provides no guidance on when to use this tool or how it differs from the many sibling tools like scrapecreators_story_highlights or scrapecreators_postreel_info. There is no mention of prerequisites, alternatives, or exclusions.

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