Read the connected account's profile

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds value beyond that by disclosing the API's hard limitation that only the connected account's profile is accessible, which is essential behavioral context for an agent deciding whether this tool can satisfy a request.

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 two sentences with no filler. It front-loads the useful field list and ends with a crucial scope limitation, making every sentence informative and earning its place.

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 simple read-only tool with no required parameters and a fully documented schema, the description is sufficiently complete. It enumerates the returned data, clarifies the account scope, and works alongside annotations that already communicate safety. No critical information is missing for an agent to call this tool correctly.

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 parameter 'account' is already fully described in the schema, including its default behavior and guidance to use list_accounts to discover valid values. The description does not need to restate this, so the schema carries the semantic load; the description adds no new parameter-level meaning.

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 identifies a specific verb and resource: reading the connected account's profile and audience. It also lists concrete fields (username, display name, bio, verified flag, follower/following counts, total likes, public video count), making the tool's purpose unmistakable. The final constraint about only seeing the connected account distinguishes it from sibling tools that access other data.

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 provides clear context: this tool targets the connected account's profile and explicitly warns that it cannot read anybody else's profile. It does not name a specific alternative tool for other profiles, but the boundary for when to use this tool is clear from the API limitation statement.

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