get_instagram_profile

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

No annotations exist, so the description carries the full burden. It partially meets it by enumerating what is returned, which is valuable given there is no output schema, but it omits whether the account is hardcoded, whether auth is required, and whether it counts only this specific handle.

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?

One compact sentence with the return fields front-loaded and no filler. The phrasing 'in.yogeshwar' inside the sentence is slightly awkward but not wasteful.

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 parameters and no output schema, the description covers the return contents, which is the main need. It still leaves an agent unsure whether the account is configurable and how this differs from the other profile tools, which is a meaningful gap in a 35-tool server.

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 declares zero parameters, so there is nothing for the description to disambiguate, and 4 is the baseline for parameterless tools. The mention of 'in.yogeshwar' usefully signals the account is fixed rather than caller-supplied.

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 names a specific verb and resource ('Get profile info... for Instagram account') and enumerates the returned fields (followers count, bio, media count). It does not differentiate itself from the similarly purposed siblings get_user_profile, get_page_profile, or get_threads_profile, so it lands at 4 rather than 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?

There is no statement about when to use this tool versus get_user_profile, get_instagram_account_insights, or get_instagram_media. The only implicit guidance is the account handle 'in.yogeshwar', which is not framed as a selection condition.

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