meta-mcp

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

No annotations provided, so description carries full disclosure burden. Fails to mention pagination behavior, reply nesting depth, rate limits, or authentication requirements. Only behavioral hint is '(conversation)' suggesting threaded 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?

Single sentence with zero waste. Action verb front-loaded ('Get replies'), parenthetical adds clarifying context without verbosity. Appropriately sized for the tool's scope.

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?

Sufficient for a read-only retrieval tool with well-documented schema, but lacks output structure description (no output schema provided) and pagination guidance. Meets minimum viable threshold but leaves operational gaps.

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%, so descriptions for post_id, reverse, limit, and after are complete in the schema. The tool description implies the need for a specific post identifier but adds no semantic detail beyond the schema definitions. Baseline 3 appropriate.

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 replies') and resource ('Threads post'), distinguishing from siblings like 'threads_get_post' (parent post) and 'ig_get_replies' (Instagram platform). The parenthetical '(conversation)' clarifies the threaded nature of the data.

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 no guidance on when to use versus alternatives like 'threads_get_posts' or 'threads_get_user_threads'. No mention of pagination strategy despite the 'after' cursor parameter existing in the schema.

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