meta-mcp

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

No annotations provided, so description carries full disclosure burden. Adds critical deprecation warning (v22.0) and valid metric enumeration. Missing: error handling, rate limits, auth requirements, or data retention details. Does not contradict annotations.

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?

Well-structured with purpose front-loaded, followed by high-value deprecation warning, then metric enumeration. Slightly redundant with schema's metric description, but the standalone list improves scanability. No filler text.

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?

Appropriate for 2-parameter tool with complete schema coverage. Deprecation warning addresses API version complexity. Gap: no output schema exists, and description doesn't clarify return structure (object, array, or scalar values), which would help the agent handle the response.

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 has 100% coverage, establishing baseline 3. Description adds value by warning about deprecated parameter values ('impressions', 'video_views') not mentioned in schema, and reinforces valid metric options. Deprecation context changes how agent should construct the 'metric' parameter.

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?

Clear specific verb ('Get') + resource ('insights/analytics') + scope ('specific media post'). Effectively distinguishes from sibling 'ig_get_account_insights' (account-level) and Threads tools by specifying 'media post' granularity.

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?

Provides specific guidance on deprecated metrics ('impressions'/'video_views') and directs to 'views' instead. Includes REEL-specific metric guidance (likes, comments, reposts). Lacks explicit contrast with account-level insights tool but implies scope through specificity.

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