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

With no annotations, the description carries the full burden, and it does disclose two non-obvious traits: an Authorization: Bearer <api_key> header is required, and each call consumes request quota. Those are exactly the kind of cost/auth facts annotations would otherwise provide. It stops short of saying what a response looks like when platform/resource vary, what happens on an invalid combination, or whether quota cost differs by endpoint.

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?

Three short sentences, front-loaded with the action and followed by the two operational constraints and the discovery hint. No filler. It could be marginally tighter, but nothing is redundant.

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?

For a generic dispatcher fronting 26 specialized siblings with no output schema and free-form params, the definition covers auth, quota, and discovery but omits the most decision-relevant fact: that responses vary by platform/resource and that dedicated tools may be preferable. Adequate to invoke, not complete enough to route confidently.

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%, so the schema already documents platform, resource, and the free-form params object. The description adds only the pointer to list_endpoints as the source of valid values, which is modestly useful for open-ended string params with no enums. Baseline 3 applies.

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?

"Fetch public social data via Socify" gives a verb and a scope, and the required platform/resource pair implies a generic endpoint dispatcher. But it never says it is a generic pass-through across platforms, nor how it differs from the 26 specific siblings (instagram_profile/info, tiktok_videos/comments, etc.) that appear to target the same data.

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 does give one actionable routing instruction: use list_endpoints to discover valid platform/resource values and params. That is real guidance for a tool whose two required arguments are open-ended strings. What is missing is the key decision rule — whether an agent should call this generic lookup or the purpose-built sibling endpoint when one exists.

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