get_profile

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the important behavioral detail that it targets the *connected* account (no ID argument, single-tenant scope) and enumerates the returned fields. It doesn't mention failure modes when no account is connected, which would have earned a 5.

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?

Front-loaded with the action, then usage conditions, then returns. The enumerated return field list mildly duplicates the output schema and is the one part that doesn't fully earn its space, but it's short and scan-friendly.

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, readOnly annotations, and a full output schema, an agent has everything needed. The description confirms the account-selection assumption (connected account) and the onboarding use case, closing the only real ambiguity.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed by framing it entirely around the connected account.

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?

States a specific verb and resource ('Get the connected Instagram account's profile') and scopes it to the single connected account, which distinguishes it from sibling insight tools like get_account_insights and get_audience_demographics. An agent can tell exactly what this returns without opening the schema.

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?

Gives explicit triggering conditions: 'Use this first to confirm which account is connected' and use it when the user asks about follower count, bio, or post count. It does not explicitly address overlap with get_account_insights for follower metrics, so the alternative routing is only partially resolved.

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