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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is fully covered by structured data. The description adds only that the returned ID is "stable numeric," which is modest but real context about the payload; it says nothing about auth requirements or what else the profile contains.

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?

A single front-loaded sentence with no filler; the verb and object lead. It is efficient, though the terseness leaves useful disambiguation unsaid.

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 zero-required-param read tool with strong annotations this is close to sufficient, and "stable numeric ID" hints at the main return value. With no output schema, however, the description never enumerates what the profile actually returns (name, picture, etc.) or how it relates to the sibling profile tools.

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?

One optional parameter with 100% schema description coverage – the schema already explains unipile_account_id, that it is not a Facebook person/Page ID, and when it is required. The description adds no meaning beyond that, so the baseline 3 applies.

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?

"Read the Facebook account owner's profile" gives a specific verb and resource, and "account owner's" implicitly separates it from facebook_get_profile (other users) and facebook_update_my_profile (mutation). It stops short of naming those siblings, so an agent must infer the boundary from wording alone.

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?

No explicit when-to-use or when-not-to-use statement, and no alternative tool is named. Usage is only implied by "account owner's" – an agent can guess this is for the authenticated account, but nothing excludes facebook_get_profile or states prerequisites.

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