meta-mcp

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

No annotations are provided, so the description carries full disclosure burden. It fails to explain side effects (what happens upon acceptance/decline), whether actions are reversible, or what the tool returns. The 'Added in December 2025' timestamp adds no behavioral clarity.

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?

The description is appropriately brief and front-loaded with the functional statement. The second sentence (version date) adds minimal value but does not significantly detract from the overall conciseness.

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 simple 2-parameter mutation tool with no output schema, the description covers the core operation adequately. However, it misses workflow context (linking to ig_get_collaboration_invites for invite discovery) that would help agents understand the full usage pattern.

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?

With 100% schema description coverage, the baseline is 3. The description adds no specific parameter guidance beyond what the schema already documents (invite_id and action enum).

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?

Description provides specific verbs ('Accept or decline') and clear resource ('collaboration invite'). It effectively distinguishes from sibling tool 'ig_get_collaboration_invites' by indicating this is a write/response action rather than a read operation.

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?

While the description implies usage context through the action verbs, it lacks explicit guidance on when to use this versus alternatives, and omits the prerequisite workflow step of obtaining the invite_id (likely via ig_get_collaboration_invites).

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