meta-mcp

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

No annotations provided, so description carries full burden. Discloses the two-step internal process and HTTPS URL requirement, but fails to mention mutation side effects (creates public post), return value format (container ID?), reversibility, or error handling behavior.

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, zero waste. Purpose front-loaded ('Publish a photo'), followed by implementation detail ('Two-step process'), then critical requirement ('Requires image_url'). Efficient structure.

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 5-parameter publishing tool with complete schema documentation, but gaps remain due to missing annotations and output schema. Description should disclose what the tool returns (post ID? container status?) and confirm the destructive/public nature of the mutation.

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%, establishing baseline 3. Description mentions image_url constraints but this merely echoes schema content ('Public HTTPS URL'). No additional semantics provided for optional parameters (caption, location_id, user_tags, alt_text) beyond 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?

Clear specific verb ('Publish') + resource ('photo to Instagram'). Explicitly names 'photo' which distinguishes from siblings like ig_publish_video, ig_publish_reel, ig_publish_story, and threads_publish_image.

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 naming and mentions internal 'two-step process' (container creation then publishing), but lacks explicit when-to-use guidance versus sibling publishing tools (e.g., when to choose photo vs carousel) or prerequisites like account permissions.

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