x_api_stream_posts_sample

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states read-only risk, bearer token prerequisites, auth resolution behavior via scopeTenantId/scopeUserId/scopeAccountId, common failure conditions, and safety warnings. This is comprehensive and goes well beyond basic expectations.

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 labeled sections and includes an example, making it easy to scan. It is long but mostly purposeful, though it repeats 'Stream sampled Posts' in the 'Use when' line, which is redundant and slightly wasteful.

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 complex streaming tool with no output schema, the description covers prerequisites, expected response shape, failure conditions, recommended related tools, and safety. It is missing detailed semantics for two auth-related parameters and does not clarify how this sample stream differs from sample10/firehose alternatives, leaving some contextual gaps.

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 explains the roles of scopeTenantId, scopeUserId, scopeAccountId, and credentialKey, plus backfill_minutes as a query integer. However, authorizationKey and preferredAuthType are left unexplained, and the exact constraint of exactly one scopeUserId/scopeAccountId is only partially clarified.

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 tool streams sampled Posts, using a specific verb and resource. However, it does not differentiate from siblings like x_api_stream_posts_sample10 or x_api_stream_posts_firehose, and 'sampled' is generic without indicating which sample tier this is.

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 provides explicit 'Use when' and 'Do not use when' guidance, and recommends alternatives like x_schema_discovery and x_query_suggestion for exploration. The 'Use when' statement is tautological, and it does not compare against other streaming tools, but the guidance is otherwise actionable.

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