get-stream-by-id

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

No annotations are provided, so the description carries the full burden. It states what is returned ('stream settings, description, subscriber count') but does not disclose behavioral traits like authentication requirements, rate limits, or data freshness. More details on the response structure would improve transparency.

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 sentence with an emoji, but it conveys the purpose and key return items efficiently. No unnecessary words; however, the emoji may be seen as informal. Could be slightly more structured.

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 no output schema and no annotations, the description provides a basic overview of what is returned ('stream settings, description, subscriber count'). However, it lacks details on exact fields, pagination, or error cases. For a simple retrieval tool, it is minimally adequate but not comprehensive.

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 100%, so baseline is 3. The description adds minimal extra meaning: it implies stream_id is numeric (matching schema) and mentions returning subscriber count, but does not elaborate on the include_subscribers parameter beyond the schema's description. No significant value added.

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's purpose: 'Get comprehensive information about a stream (channel) when you have its numeric ID.' It uses a specific verb (get) and resource (stream) and distinguishes from siblings like get-stream-id (which likely retrieves ID) and get-subscribed-streams.

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 some guidance ('when you have its numeric ID') but does not explicitly mention when not to use this tool or name alternatives. Siblings like get-stream-id (for when you don't have the ID) are not referenced.

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