Look up accounts

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

The read-only and open-world traits are already covered by annotations, and the description adds what is returned (profile and membership flags) and the batch cap. It does not describe missing-account behavior, authentication needs, rate limits, or return shape.

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 front-loaded sentence with no wasted text. It is appropriately concise, though highly compressed given the parameter ambiguity.

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 three-parameter read-only lookup with no output schema, the description identifies the returned data category and batch limit. It remains incomplete on how the id/username/account inputs interact and on output details beyond the brief phrase 'profile and membership flags.'

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 only 33%, with only the account parameter documented in-schema. The description partially compensates by indicating singleton account usage and lookup by up to 100 usernames or IDs, but it does not explain precedence when multiple input modes are supplied or exact ID formats beyond the schema's note on account.

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 a specific resource and content: profile and membership flags for an account, plus batch scope for up to 100 usernames or IDs. It is more specific than the title, but it does not explicitly distinguish itself from siblings such as ca_me or ca_find_people.

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?

It implies usage for singleton or batch account lookups by specifying one account or up to 100 identifiers. However, it gives no explicit when-to-use/when-not guidance or alternatives, such as using ca_me for the authenticated user or ca_find_people for discovery.

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