x_api_stream_likes_firehose

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses read-only risk, bearer token requirement, environment-selection behavior for scoped credentials, expected response shape, common failure conditions, and safety warnings about sensitive data. This far exceeds typical tool descriptions.

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 well-structured with clear labeled sections, making it easy to scan. It includes some redundancy, such as the tautological 'Use when: Stream all Likes' and repeated read-only statements in Risk and Safety warnings, but overall each section adds practical value.

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?

Given the tool's complexity (10 parameters, no output schema, no annotations), the description is remarkably complete. It covers purpose, usage boundaries, auth prerequisites, environment selection, parameter constraints, response shape, failure modes, recommended companion tools, safety, and an example.

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 0%, so the description must compensate. It documents backfill_minutes, partition, start_time, and end_time with types and required status, and explains scopeTenantId/scopeUserId/scopeAccountId/credentialKey semantics in the environment-selection section. However, authorizationKey and preferredAuthType are not mentioned, leaving a minor gap.

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 opens with 'Stream all Likes,' which clearly identifies a specific verb and resource, and 'all' indicates the firehose scope. However, it does not explicitly contrast with sibling tools like x_api_stream_likes_sample10 or x_api_stream_likes_compliance, so some differentiation is left to the tool name.

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 'Use when' and 'Do not use when' sections, but 'Use when: Stream all Likes' is essentially a tautology. It does offer useful exclusions for exploratory use and points to x_schema_discovery/x_query_suggestion, but it fails to give guidance on when to choose this firehose over the sibling likes streaming tools.

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