meta-mcp

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

No annotations provided, so description carries full burden. Mentions 'public info' indicating data visibility level, but omits explicit read-only classification, rate limits, or requirement that target must be Business/Creator account type.

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 11-word sentence with action front-loaded ('Look up'). Zero redundancy or filler content. Efficiently conveys core functionality without unnecessary elaboration.

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?

Adequate for a 2-parameter lookup tool with simple flat schema. Given no output schema or annotations, could benefit from explicit mention of the Business/Creator account requirement and error behavior (e.g., private accounts), but covers the basic contract sufficiently.

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%, establishing baseline 3. Description reinforces 'by username' matching the required parameter, but adds no further semantic context like validation rules or field format details beyond what the schema already provides.

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 uses specific verb 'Look up' with clear resource 'another Instagram Business/Creator account's public info' and distinguishes from sibling ig_get_profile by emphasizing 'another' (third-party) lookup capability.

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 implied usage context by specifying 'another' account (suggesting use for external lookups vs. own profile), but lacks explicit when-to-use guidance or named alternatives like ig_get_profile for authenticated user data.

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