account_info

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

With no annotations, the description carries full responsibility for behavioral disclosure. 'Live' indicates real-time data, but the description does not mention how the account identifier is interpreted, what happens for invalid accounts, whether any authentication is required, or what 'etc.' includes. This is a significant gap for a tool with zero annotation coverage.

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 tight sentence that front-loads the core purpose and lists illustrative return fields. The trailing 'etc.' is slightly vague but does not undermine overall efficiency.

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?

For a tool with one optional parameter and an output schema, the description covers the main purpose and return content. However, the missing parameter semantics (what 'account' is and default behavior) leaves an agent guessing about how to invoke it correctly, so it is not fully complete.

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?

Schema description coverage is 0%, so the description must explain the 'account' parameter. It implies the parameter selects the target account, but it never specifies whether it expects a username, ID, handle, or URL, nor what the default null behavior means. The description adds only marginal meaning beyond the bare schema.

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 states the resource ('one account') and the content of the snapshot ('username, name, followers, media count, etc.'), which distinguishes it from sibling list_accounts. However, it lacks an explicit retrieval verb like 'get' or 'fetch', relying on the noun phrase 'Live profile snapshot' to convey the action.

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 'one account' scope implies use when a single account's profile data is needed, which loosely separates it from list_accounts. But there is no explicit guidance on when to use this instead of similar siblings such as get_profile or business_discovery, and no exclusion criteria are provided.

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