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 mention whether this retrieves the authenticated user's profile or supports lookups, what specific fields are returned, rate limits, or error conditions. Only hints at account type constraint ('Business/Creator').

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 that is immediately front-loaded with the core action and target. No redundant or filler text. Appropriate length for the simplicity of the tool interface.

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?

Lacks output schema and annotations, yet the description does not compensate by describing what profile information is returned (e.g., bio, follower count, profile picture). Does not clarify if this fetches the current authenticated account or supports arbitrary lookups. Insufficient for an API tool with 30+ siblings.

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?

Input schema contains zero parameters. Per evaluation rules, 0 parameters establishes a baseline score of 4. The description implies no configuration is needed (likely retrieves authenticated user's profile), which aligns with the empty schema.

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?

Clearly states the verb ('Get') and target resource ('Instagram Business/Creator account profile information'). The 'Business/Creator' qualifier helps distinguish from personal account tools, though it could explicitly differentiate from the sibling 'threads_get_profile' tool.

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 this versus 'threads_get_profile' or other account information tools. Does not mention prerequisites like requiring Business/Creator account authentication or permissions.

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