x_api_get_rule_counts

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

No annotations provided, so the description carries full burden. It discloses read-only risk, required bearer token, environment-selection behavior for scoping parameters, expected response shape, common failure conditions, and safety warnings about sensitive data. This is comprehensive behavioral context.

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 front-loaded with a clear one-line purpose. Some redundancy exists between the opening sentence and the 'Use when' section, but overall the content is organized and avoids excessive verbosity.

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?

Despite lacking an output schema, the description provides the expected response shape, failure conditions, prerequisites, an example, and safety warnings. It also references related tools for context. This is a complete guide for using the tool correctly.

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 role of scopeTenantId, scopeUserId/scopeAccountId, and credentialKey in auth resolution, but does not elaborate on authorizationKey or preferredAuthType. The statement 'no endpoint-specific parameters' is vague and adds limited value. Partial compensation for schema gaps.

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 the tool's purpose as 'Get stream rule counts' with a specific verb and resource. While the name and description are nearly identical, the resource is clear and distinct from sibling rule tools like x_api_get_rules. No explicit differentiation from alternatives, but the purpose 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?

Provides a 'Use when' section that directly restates the purpose and a 'Do not use when' that advises against exploratory use, suggesting x_schema_discovery or x_query_suggestion instead. It also lists recommended prerequisite and follow-up tools, giving practical context for when this tool fits in a workflow.

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