Get publication engagements

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so "Reads account data" is largely redundant. The OAuth scope requirement (publications:read) is genuine added context beyond the annotations, but nothing is said about return format, result size, or pagination behavior.

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 short sentences, front-loaded with the operation, with no filler. However, the extreme brevity comes at the cost of substance rather than being tight-but-complete.

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?

For a seven-parameter reporting tool with no output schema, the description never indicates what engagement data is returned or in what shape, and says nothing about how the date, granularity, and number_of_days parameters interact. The auth note alone is insufficient for an agent to call this confidently.

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% – all seven parameters carry defaults, enums, ranges, and format notes. The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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?

"Get publication engagements" names a verb and resource, but it essentially restates the tool name and title without saying what an 'engagement' actually contains (opens, clicks, unsubscribes, etc.). No sibling differentiation is needed since no other engagement tool exists, but the purpose remains vague about the payload.

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 description gives no when-to-use context and names no alternatives, even though siblings like get_post_aggregate_stats and ad_network_reports_summary cover adjacent reporting territory. The only guidance is auth-related, not selection-related.

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