get_profile_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify permissions required, rate limits, error conditions, or what happens if no account_id is provided (beyond the schema's note). For a tool with zero annotation coverage, this lacks critical context about safety and operational constraints.

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 description is a single, efficient sentence that front-loads the core purpose ('Get Instagram business profile information') and adds specific examples ('including followers, bio, and account details') without redundancy. Every word earns its place, making it highly concise and well-structured.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the return values include (beyond vague examples like 'followers'), error handling, or authentication needs. For a tool with no structured support, the description should provide more operational context to be fully helpful to an agent.

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 description adds no parameter-specific information beyond what the schema provides. The schema has 100% coverage with a clear description for the single optional parameter. Since the description doesn't elaborate on parameter usage (e.g., when to omit account_id), it meets the baseline of 3 where the schema does the heavy lifting.

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 clearly states the verb ('Get') and resource ('Instagram business profile information') with specific examples of what information is retrieved ('followers, bio, and account details'). It distinguishes from siblings like 'get_account_insights' or 'get_media_posts' by focusing on general profile data rather than analytics or content. However, it doesn't explicitly contrast with 'business_discovery', which might also retrieve profile info, so it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a business account), exclusions (e.g., not for personal profiles), or compare to siblings like 'business_discovery' or 'get_account_pages'. The agent must infer usage from the tool name and description alone, which is minimal.

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