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

The description is consistent with the readOnlyHint and destructiveHint annotations, and adds the conceptual detail that profiles group social accounts. It does not describe pagination, ordering, or response shape, but for a read-only list tool the annotations carry much of the burden.

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 short and front-loaded with the core behavior. The second sentence provides helpful domain context without adding unnecessary length, though it is not strictly required to invoke the tool.

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 parameterless, read-only list tool with an output schema, the description is sufficient for selecting and invoking the tool. The only missing contextual detail is possible behavior such as pagination or ordering, which is not essential here.

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 has zero parameters, so there is no parameter-usage burden for the description to carry. The empty schema is consistent with the stated behavior of listing all profiles without filters.

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 clearly states the verb and resource: 'List all profiles.' The second sentence adds useful conceptual context by explaining that profiles group multiple social accounts together. It does not explicitly differentiate from sibling tools like profiles_get or account_groups_list_account_groups, but the intent is unambiguous.

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 use case is implied: an agent needing the full set of profiles should call this tool. However, there is no explicit guidance about when to prefer this over similar list tools such as accounts_list or account_groups_list_account_groups.

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