gcfr_top_slowest_streams

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

Annotations are absent, so the description must disclose behavior. It mentions top_n bounds and business_date default, but does not state read-only nature, side effects, ordering direction beyond 'slowest', or any permission requirements. This is a minimal disclosure for a query tool.

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?

Two sentences, front-loaded with the core purpose, no redundancy. All sentences add value, including parameter constraints and default behavior. Excellent conciseness.

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?

Both parameters are addressed with bounds and defaults. Output schema exists, so return details are not needed in the description. The only notable gap is the unspecified business_date format/timezone for 'today', which is minor for a simple query tool.

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 has 0% description coverage, so description must compensate. It adds top_n range (1-50) and default 10, and business_date defaulting to 'today'. However, it omits date format, timezone, and the exact meaning of 'elapsed duration' relative to parameters. Partial coverage only.

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?

Clear verb 'Show' with specific resource 'streams' and qualifier 'slowest by elapsed duration'. Immediately distinguishes from sibling gcfr_top_slowest_processes by targeting streams, not processes.

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?

No guidance on when to use this tool versus the many sibling tools (e.g., process versions, status tools). No mention of exclusions or scenarios where the stream-specific tool is preferred over others.

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