meta-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides minimal information. It does not clarify read-only safety, rate limits, what 'published' implies (vs. drafts), or the return data structure. The agent must infer safety from the verb 'get'.

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 single sentence is efficiently worded with no redundancy. However, given the lack of annotations and the need to distinguish from numerous siblings, the description is arguably too minimal rather than appropriately concise.

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?

Incomplete for a tool with 5 parameters, no annotations, and no output schema. Critical gaps remain regarding resource ownership (authenticated user's posts), pagination behavior (how cursors relate to time ranges), and relationship to sibling tools. The description does not compensate for missing structured metadata.

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%, so the schema adequately documents all five parameters (limit, since, until, after, before). The description adds no parameter-specific context, meeting the baseline expectation when the schema is self-documenting.

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?

The description states the basic action (get/list) and resource (Threads posts), but fails to specify whose posts (authenticated user vs. arbitrary) or how it differs from siblings like 'threads_get_user_threads' or 'threads_get_post' (singular). The scope is ambiguous given the API context.

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?

No guidance provided on when to use this versus 'threads_search_posts', 'threads_get_user_threads', or 'threads_get_post'. No mention of pagination strategies (time-based vs. cursor) or prerequisites like authentication requirements.

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