p4_stream

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 only states what the tool does (get stream spec details) without mentioning any behavioral traits such as whether it requires an existing workspace, what happens if the stream is not found, or whether it only reads data. The description adds no context beyond the action itself.

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 short sentence that is front-loaded and contains no filler. It earns its place in terms of conciseness, though it is sparse on detail.

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 there is no output schema and no annotations, the description should compensate with more context. It does not specify what a stream spec is, what information will be returned, when to use this tool vs p4_streams, or any error/edge-case behavior. For a simple 2-parameter tool, an agent would still likely need additional clarification to know exactly what to expect.

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%: the stream parameter is described as 'Stream path/name (required)' and workspacePath as 'Path to workspace directory (optional, defaults to current directory)'. The description adds no additional meaning beyond the schema, so baseline 3 applies.

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 uses a specific verb ('Get') and resource ('stream spec details'), making it clear the tool retrieves details about a single stream spec. It does not explicitly differentiate from the sibling p4_streams, which likely lists streams, but the singular 'stream spec' implicitly indicates a specific stream rather than a listing.

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 no guidance on when to use this tool versus alternatives such as p4_streams, p4_fstat, or p4_describe. There is no mention of prerequisites, expected inputs, or cases where another tool would be more appropriate. An agent must infer usage from the tool name and schema.

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