meta-mcp

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

No annotations provided, so description carries full burden. Discloses critical behavioral constraints: required permission ('instagram_manage_messages') and policy restrictions (messaging window limitations). Lacks disclosure of return values, idempotency, or error conditions.

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 with zero waste: purpose front-loaded, followed by permission requirement, then usage constraints. Every sentence provides distinct, high-value information.

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?

Given the 2-parameter input with 100% schema coverage and absence of output schema, the description adequately covers the complex policy requirements (permission and messaging windows). Minor gap regarding return value documentation, but constraint coverage is the critical need here.

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% (both recipient_id and message fully documented). Description does not add parameter-specific semantics beyond what the schema provides, meeting the baseline expectation for high-coverage schemas.

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 ('Send') + resource ('DM') clearly stated. Distinguishes from sibling read operations (ig_get_messages, ig_get_conversations) by identifying itself as the write/mutation action.

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 clear constraints on when the tool can be used (24hr/7-day window, requires prior incoming message). However, does not explicitly name complementary tools (e.g., ig_get_conversations to check eligibility) or explicit 'when not to use' alternatives.

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