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

No annotations were provided, so the description must carry the full behavioral burden. It does disclose the shape of the response (the specific KPI metrics), which matters because no output schema exists. However, it says nothing about read-only semantics, credit consumption, caching, or authorization requirements, which are exactly the traits annotations would normally cover.

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?

It is a single dense sentence with the resource and the metric list front-loaded and no filler. Every clause earns its place by naming a specific returned metric.

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 one-parameter read tool with no output schema, the description is nearly complete: it enumerates the returned KPIs so the agent can judge relevance without calling it. The remaining gap is that it doesn't position the tool against the several sibling analytics tools (engagement trends, posting insights, profile preview).

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?

The single parameter has 100% schema description coverage and is already documented as a 'Tracked profile ID from list_profiles.' The description adds nothing about the parameter, which is fine here because the schema covers it, but it provides no added meaning.

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 definition pairs a specific verb ('Get KPI summary') with a specific resource ('tracked profile') and enumerates the metrics returned (posts, engagement breakdown, posts/week, trend, top format, goal status). An agent knows exactly what this returns, but nothing distinguishes it from siblings like preview_profile, get_posting_insights, or get_engagement_trends.

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 explicit when-to-use or when-not-to-use guidance, and names no alternative. The closest thing to routing information is the schema's note that profile_id comes from list_profiles, which implies a two-step workflow but never states it in the description itself.

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