meta-mcp

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

No annotations provided, so description carries full burden. Explicitly discloses irreversibility ('This action is irreversible') and authentication requirements, providing critical safety context for a destructive operation.

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 sentences, front-loaded with action. Every sentence earns its place: defines scope, warns of irreversibility, states permission requirement. No wasted words.

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?

Adequate for a single-parameter destructive tool with no output schema. Covers critical aspects (scope, irreversibility, permissions) though could mention error cases (e.g., media not found).

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 coverage is 100% with media_id fully described. Description adds semantic context about what types of media can be deleted but does not elaborate on parameter format or validation beyond the schema.

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?

Specific verb 'Delete' with resource 'Instagram media post' and explicit scope enumeration '(posts, carousels, reels, stories)' distinguishes from sibling ig_delete_comment (comments) and threads_delete_post (Threads content).

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?

Implies usage through scope definition but lacks explicit when-to-use guidance vs alternatives. Notes permission requirement ('Requires instagram_manage_contents permission') which aids usage but doesn't constitute full decision guidelines.

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