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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only says 'Story Highlights' and provides zero information about side effects, permissions, rate limits, return behavior, or any other operational characteristics.

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 two words, which is under-specification rather than effective conciseness. Every sentence should earn its place, but here the placeholder-like text does not convey enough substance to be considered concise.

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?

The tool has no output schema, no annotations, and a minimal two-word description. For a scraping tool with two optional parameters and a closely related sibling tool, the description fails to explain return values, usage edge cases, or how it differs from existing alternatives, making it completely inadequate.

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 100% since both parameters (handle and user_id) have descriptions in the schema. Per the baseline for high coverage, a score of 3 is appropriate even though the tool description itself adds no parameter meaning beyond what the schema already provides.

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 'Story Highlights' is a noun phrase that simply restates the tool name without specifying an action or resource. It fails to indicate whether the tool retrieves, lists, or manages story highlights, and does not distinguish it from the sibling tool scrapecreators_highlights_details.

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 is provided on when to use this tool versus alternatives such as scrapecreators_highlights_details or other Instagram-related tools. The description gives no context, prerequisites, or exclusions.

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