meta-mcp

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

No annotations provided, so description carries full disclosure burden. It successfully communicates API versioning behavior (v22.0 deprecation), but omits other behavioral traits like rate limits, authentication requirements, or return data structure.

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 with zero waste. Front-loaded with the core action, followed immediately by a critical deprecation note. Every word 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?

For a read-only insights tool with 100% schema coverage, the description adequately covers the primary complexity (deprecated metrics). No output schema exists, so return value explanation is not required. Could improve by mentioning permission requirements.

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?

While schema has 100% coverage, the description adds critical semantic context about valid metric values. It explains that certain metrics were deprecated and suggests specific replacements ('views', 'reach', etc.), providing value beyond the schema's simple list of valid options.

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 specific action ('Get') and resource ('Instagram account insights') clearly. However, it does not explicitly differentiate from sibling tool 'ig_get_media_insights' which retrieves media-level insights rather than account-level.

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 implied usage guidance through the deprecation warning, instructing users to avoid deprecated metrics like 'impressions' in favor of 'views' and 'reach'. Lacks explicit guidance on when to choose this tool over 'ig_get_media_insights' or 'threads_get_user_insights'.

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