get_instagram_profile

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only notes the profile must be 'public', which hints at a limitation, but does not mention return format, rate limits, error behavior, or what data is included. This is sparse for a tool with no structured behavioral annotations.

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 sentence with no unnecessary words. It front-loads the verb and resource, then specifies the input format. It is concise without sacrificing clarity.

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?

With no output schema, the description should explain what 'profile data' includes, but it remains vague. It also lacks details on limitations for private profiles, expected errors, or result structure. While the tool is simple, the description is under-specified for an agent to know what to expect.

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 schema has zero description coverage, but the description compensates by adding meaning to 'instagram_url_or_username': it clarifies the string can be either a username or a URL, and must be public. This goes beyond the bare type string, giving the agent essential usage context.

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 the specific verb 'Fetch' and clearly identifies the resource as 'Instagram profile data', with a parameter accepting a username or URL. This distinctly separates it from sibling tools like get_facebook_profile and scrape_website, making the tool's purpose immediately clear.

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 implies the tool is used when you need Instagram profile data, but provides no explicit guidance on when to use it versus alternatives like get_personal_profile or scrape_website. There are no stated exclusions or comparison to sibling tools, leaving the agent to infer usage context.

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