socials_get_page_content

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

With no annotations, the description carries the burden of disclosure. It reveals useful behavioral traits: 'auto-scroll' on search results and the ability to 'switch comment sort (top/newest) before scraping.' These go beyond basic functionality and help set expectations.

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 concise and well-structured: one sentence states the core purpose, a second elaborates on YouTube-specific behaviors. Every sentence earns its place without unnecessary fluff.

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?

Despite lacking an output schema, the description explains what is returned ('video cards', 'structured video metadata plus comments') and mentions configurable options like comment sorting. It does not cover error handling or limits, but for a scraping tool of moderate complexity, it is sufficiently complete.

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 100% coverage with each parameter having a clear description. The tool description does not add extra parameter meaning beyond the schema; it only indirectly references comment_sort. Thus, the schema does the heavy lifting, so a baseline score of 3 is appropriate.

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 clearly states the tool's function: 'Get structured content from the pinned agent tab.' It further distinguishes between YouTube search and watch page behaviors, making it specific and different from sibling tools like socials_get_active_tab or socials_get_feed.

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?

It provides clear context for when to use the tool, explaining what happens on YouTube search vs. watch pages. However, it does not explicitly mention alternatives or when not to use it, though the behavior descriptions implicitly guide usage.

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