browse_remote_directories

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered. The description usefully reinforces that this reads live server state ('actual remote directories'), but adds nothing about return shape, whether hidden files or symlinks appear, or any permission/size limits.

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, each earning its place: the first defines the action and scope, the second the workflow trigger. The purpose is front-loaded with zero filler.

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?

For a read-only, fully-annotated, fully-documented exploration tool this is close to complete; the workflow cue is genuinely helpful. The only notable gap is that with no output schema, the description never states what is returned (a listing? entries with types?), forcing the agent to infer.

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% — path, project and environment are all documented in the schema with defaults. The description adds no extra semantics such as path syntax, relative vs. absolute handling, or what 'environment' means for browsing. 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?

States a specific verb pair (Inspect/browse) and resource (remote directories and files on the hosting server), which is more concrete than a bare name restatement. It doesn't explicitly name the sibling it contrasts with (set_remote_path / download_remote_file), but the 'explore before picking a destination' framing makes the distinction inferable.

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?

'Use this to explore what folders exist on the server before picking a remote deployment destination' gives a clear trigger condition tied to the deployment workflow. No explicit when-not or named alternatives (e.g., vs. set_remote_path) are provided, so it falls short of a 5.

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