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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not required to establish safety, yet it reinforces this and adds genuinely new behavioral detail: bot_views excludes security scanners, the result includes top engaged accounts with interaction_summary, and it warns that company names and page fields are customer data rather than instructions. It omits output format and pagination/limit behavior, keeping it below a 5.

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?

Front-loaded with the core action, then scope, then returned fields, with the injection-defense note at the end. Dense but every clause carries information; the '($0.00)' cost parenthetical is mild redundancy but useful context for an agent deciding whether to call it.

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 and only two optional parameters, the description carries the return-value burden and does so by enumerating the metrics, including the bot-filtering nuance. Limits are covered by the schema (1-50, default 20), so no material gap remains for correct 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 100%, so the baseline is 3. The description adds the semantics of list_id (scoping to one hosted list versus workspace-wide) and clarifies that the tool returns top engaged pages/accounts, but adds no format, default, or interaction detail beyond what the schema properties already state.

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 opens with a specific verb and resource ('Read ... hosted page engagement analytics') and names the two possible scopes (workspace-wide and list_id-scoped), plus enumerates the metrics returned (human_views, bot_views, engaged_pages, cta_clicks, avg_dwell_seconds, top engaged accounts). It does not explicitly contrast itself with siblings such as get_rows or export_list, but the resource is distinct enough that an agent can identify it without opening the schema.

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?

Scope choice is implied ('workspace-wide or list_id-scoped'), which tells the agent the tool works with or without a list filter, but there is no explicit when-to-use guidance, no statement of when another tool (e.g. get_rows, export_list) would be preferable, and no prerequisites named. Usage is inferable rather than directed.

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