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 and successfully discloses the 7-day rolling rate limit and workflow position. It could improve by mentioning what happens when a hashtag is not found (error vs null response), but the rate limit disclosure is excellent.

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?

Two sentences with zero waste: first establishes purpose, second covers workflow dependency and rate limits. Every word earns its place.

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 single-parameter lookup tool with no output schema, the description is complete. It covers purpose, prerequisites, rate limits, and implicitly the return value (hashtag ID). No additional context is needed for correct invocation.

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?

The input schema has 100% description coverage ('Hashtag name to search (without #)'), so the description appropriately focuses on higher-level concerns rather than repeating parameter details. It meets the baseline 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?

The description states the specific action (search for hashtag ID), the input method (by name), and distinguishes itself from siblings by clarifying it returns an ID rather than media content (unlike ig_get_hashtag_recent/top).

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?

Explicitly states the prerequisite relationship: 'Required before querying hashtag media,' guiding the agent to use this before ig_get_hashtag_recent/top. Also discloses the critical rate limit constraint (30 unique hashtags per 7-day window) that governs when it should be used.

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