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

With no annotations provided, the description carries full responsibility for disclosing behavior. The single word 'Snapchat' reveals nothing about whether this is a read-only operation, what data it returns, or any side effects. It is entirely uninformative.

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 a single word, which is under-specification rather than conciseness. It fails to provide any meaningful content while the tool clearly requires more context given its many siblings and single parameter.

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 being a simple one-parameter tool, the description is completely inadequate. It lacks any indication of what the tool returns, how the handle is used, or any differentiating details from the numerous sibling tools. No output schema compounds the gap.

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 description coverage is 100% (the only parameter 'handle' has the description 'Snapchat username'), so the baseline is 3. However, the description adds no additional meaning beyond the schema, and the parameter description is essentially a restatement of the property name.

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 is just 'Snapchat', which restates the tool's name and provides no verb or resource. It does not state what action the tool performs (e.g., 'Scrape Snapchat profile data'), nor does it distinguish from the many sibling scrapecreators_* 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?

There is no guidance on when to use this tool versus the extensive list of sibling tools. No context, prerequisites, or alternative references are provided.

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