List account tools

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Live lookups' hints at read-only, platform-specific data, but the description does not state that listing is non-mutating, whether an account connection is required, or what happens when no tools are available.

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 compact sentence with useful examples and no filler. It is front-loaded with the key idea ('per-account live lookups') and easy to scan, though it sacrifices important guidance for brevity.

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 1-parameter list tool without an output schema, the description is still incomplete: it doesn't define what the returned list contains (tool names? endpoints? metadata?), nor how this relates to run_account_tool. An agent would need to guess the output shape and next steps.

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 schema has zero description coverage for accountId, and the description only says 'Per-account' without explaining that accountId identifies the target account or clarifying expected format/value. The single parameter is inferable from context, but the description adds little beyond the 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 a specific resource ('per-account live lookups') and gives concrete examples (Reddit flairs, Pinterest boards), making the listing intent clear. It doesn't explicitly contrast with run_account_tool, but the title and examples are enough to identify the tool's purpose.

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?

There is no explicit when-to-use guidance or mention of alternatives. The phrase 'available for the account's platform' implies you'd call this before running a lookup, but the description doesn't say to pair it with run_account_tool, nor does it state when NOT to use it.

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