get_account_analytics

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a real auth requirement (X Premium) and a failure mode (unsupported layouts return no metrics, i.e. empty results). It does not cover rate limits or pagination, but the added behavioral context is meaningful.

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 tight sentences with no filler, and the core scoping statement is front-loaded. The jargon ("observed paywall") is slightly opaque but costs little.

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?

An output schema exists so return values need not be described, and the auth/layout caveats are covered. The gap is parameter meaning: with 0% schema coverage and one required param of unclear semantics, the definition is not complete enough for confident invocation.

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 0% for two parameters, and the description never explains what "account" refers to (the owner handle? a target?) or what "limit" bounds. With the schema contributing nothing, the description needed to compensate and does not.

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?

It gives a specific verb and resource ("Read ... X analytics availability"), but "availability" is genuinely ambiguous: it is unclear whether the tool returns metrics or a boolean about whether analytics are available, especially since the same sentence references "no metrics" and "local action metrics." It does differentiate from siblings ("Distinct from local action metrics and public post counts"), which lifts it above a vague statement.

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 gives one conditional prerequisite ("Requires X Premium when the observed paywall says so") and names contrasting sibling outputs, implying when this tool is appropriate. However, it never states an explicit when-to-use trigger or tells the agent which sibling to call instead of this one.

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