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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds that retrieval needs no API key, which is useful operational context, but it does not disclose output shape or how long responses are paged; the pagination detail is present in the schema, not the description. No contradiction with annotations.

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 main purpose is front-loaded and every parenthetical earns its place by clarifying a topic. It is dense and somewhat hard to scan as a single long sentence, but there is no filler or redundant repetition of schema fields.

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?

Together with the schema and annotations, the description covers topic semantics, defaults, pagination behavior, and auth requirements, leaving little needed to invoke the tool correctly. The main gap is the lack of explicit guidance about sibling tools that share topic names, which could cause a misrouted call if the agent wants live data rather than documentation.

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 schema already documents both parameters with 100% coverage, so the baseline is 3. The description adds real value by defining each topic in parentheses and introducing the 'platform slug' concept with examples, which goes beyond the schema's bare enumeration.

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 starts with a specific verb and resource: 'Retrieve SocialCrawl API documentation.' It then enumerates every topic value with a gloss, so an agent knows exactly what kind of content is returned and can distinguish this doc-lookup tool from sibling data/action 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 clearly implies the tool is for documentation lookup and adds a useful prerequisite ('No API key required'). However, it never explicitly addresses overlaps with sibling tools like socialcrawl_pricing, socialcrawl_monitors, or socialcrawl_discover, even though those topics appear in the same docs. The agent is left to infer that live data should come from siblings rather than from this documentation tool.

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