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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile is covered. The description adds a genuinely useful non-schema fact: the call costs 8 credits, which nudges the agent toward cheaper siblings when appropriate. It does not disclose anything about timeouts, rate limits, or what an empty/private profile returns.

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?

Two compact sentences with no wasted clauses, and the payoff plus cost are stated up front. The trade-off is that the brevity comes from underspecification rather than discipline.

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, the description must carry the return-value burden, and it does name the payload shape at a high level. However, 'averages' is undefined (average of what metric?), and the ranking rule for outperforming posts is left ambiguous, which matters for a tool whose whole point is surfacing top performers.

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 coverage is only 67%: handle and limit are documented in-schema, but platform is a bare enum with no description. The description adds nothing about any of the three parameters, and 'the posts that most outperformed their own average' obliquely relates to limit without clarifying selection logic.

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 identifies the resource ('A creator's profile') and the two payload elements (averages, outperforming posts), which is informative. But it is a noun-phrase fragment with no verb, and it never contrasts itself with near-neighbors like analyze_post, get_account, or similar_content, so the agent must infer what 'analyze' means here.

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 guidance is the price signal ('Costs 8 credits'), which hints that this is a heavier operation than the plain read siblings. There is no statement of when to pick this over analyze_post, read_post, or get_account, and no exclusions or preconditions.

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