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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context by listing the sections the generated report will contain, telling the agent what it is actually producing. It omits cost/latency expectations, which matter for a 'comprehensive' generation call.

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 sentences, front-loaded with the action and the deliverables, followed by the usage trigger. The content enumeration in sentence one is long but each item tells the agent what the output contains, so it earns its place.

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 usefully compensates by naming the report's sections, which is exactly the return-value detail an agent needs here. The remaining gap is the absence of any note about the report's cost or whether the account must be monitored first, which the sibling tools suggest may be a prerequisite.

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% and both optional parameters have enums with self-explanatory values (summary/detailed, weekly/monthly). The description adds nothing about format or period beyond the schema, so the baseline 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?

States a specific verb (generate) plus resource (Instagram analytics report) and enumerates the report's contents: executive summary, growth analysis, engagement metrics, top posts, recommendations. The word "Instagram" implicitly separates it from generate_tiktok_report, but it never names that sibling explicitly even though the unprefixed tool name invites confusion.

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?

"Use this when someone asks for a report, performance review, client summary, or account audit" gives concrete, recognizable request triggers. It provides no negative guidance, however, and never routes the agent away from granular siblings such as get_account_stats or get_growth_summary when the user only wants a single metric.

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