Account 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 word 'Live' usefully signals a fresh upstream fetch rather than cached data, but nothing is said about rate limits, latency, or what happens when the default account is unauthenticated or missing.

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 front-loaded sentence with no filler, and the field list is informative rather than redundant. It reads slightly like a return-value inventory, which makes the core action ('fetch this account's profile') implicit, but nothing is wasted.

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 enumerated fields (username, biography, followers, media count, picture) usefully describe the returned shape, and annotations cover the read-only, open-world nature. For a one-optional-parameter read tool this is nearly sufficient; only guidance on default-account errors and sibling selection is missing.

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 single 'account' parameter is fully documented in the schema (100% coverage), including the omit-for-default behavior, so the description owes nothing extra. It adds no meaning beyond the schema, which matches the baseline 3 when schema coverage is complete.

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 the resource (a connected account's profile) and enumerates exactly what it returns, so an agent can tell it fetches profile data rather than metrics or account lists. It never explicitly differentiates from siblings such as get_account_insights or list_accounts, and the verb is only implied by 'Live profile', keeping it below a 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 of when to call this versus alternatives like list_accounts (to enumerate accounts) or get_account_insights (for metrics). The only implicit hint is that it applies to a single connected account, leaving routing between siblings entirely to the agent.

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