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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety and side-effect profile is covered. The description adds real value beyond that: credit cost, 'Repeated requests may purchase data again', and the face-visibility requirement. However, it contradicts itself on cost ('at least 10 Nexscope credits' vs '1 credit per request'), which leaves an agent unsure of the actual charge.

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 useful preamble is front-loaded and efficient, but it is followed by raw, duplicated API-doc boilerplate: a repeated title, 'API View Pricing', a second restatement of purpose and face requirement, and conflicting credit statements. Roughly half the text is redundant or contradictory rather than informative.

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?

With no output schema, describing the return shape (ageRange bounds, gender, confidence) is necessary and done well, and cost plus the face precondition are covered. What's missing is what happens on failure (no face detected, invalid URL, unsupported platform), which matters for an open-world lookup tool.

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?

There is a single required parameter with 100% schema description coverage ('URL to users social profile'), so the schema already carries the semantics and the baseline is 3. The description's claim that the target must contain a clear, visible face adds a little meaning (the URL must resolve to a usable profile photo), but it doesn't specify accepted URL formats or platform constraints.

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 names a specific verb and resource: estimate a creator's age and gender from their profile photo using AI. It also states the returned fields (ageRange with low/high bounds, gender, confidence). It does not distinguish itself from sibling creator/profile tools such as social_find_social_profiles or social_tiktok_user_audience, which prevents a 5.

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 only conditional guidance is a precondition ('The profile photo must contain a clear, visible face'), which shapes the inputs correctly but is not when-to-use guidance. There is no statement of when this tool applies instead of the many sibling creator-enrichment tools, and no exclusion of cases.

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