sharkd_follow

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

No annotations provided, and the description fails to disclose any behavioral traits. It does not mention side effects, required session state, or performance implications. The agent has no insight into what happens when the tool is invoked.

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 single sentence is concise but insufficient. It omits essential information, making it under-specified rather than efficiently concise. A longer description with more structure would be more helpful.

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 absence of annotations, 4 parameters with no schema descriptions, and an output schema that is not referenced, the description is incomplete. It fails to define the tool's return value, prerequisites, or behavior, leaving the agent with significant uncertainty.

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 explain parameters. Only 'protocol' and 'display_filter' are hinted, but 'session_id' and 'timeout' are completely undiscussed. No syntax or examples are given for the parameters.

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 follows a stream using protocol and display filter, but 'follow a stream' is vague and doesn't specify what that entails (e.g., reconstructed data, timings). Sibling 'llm_follow_stream_hint' suggests a related purpose, but no clear differentiation.

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 vs alternatives (e.g., other sharkd tools, llm_follow_stream_hint). No context on prerequisites or preferred scenarios.

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