Analyze Remote Project Structure

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds that it uses SSH and runs commands, which is useful, but does not disclose additional behavioral details like rate limits, required permissions, or potential command execution overhead.

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 that front-loads the purpose, but the list of detected items could be better structured (e.g., bullet points) for readability. No redundancy, but slight improvement possible.

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?

The description explains what the tool inspects but fails to mention what it returns or whether any authentication/SSH setup is required. Given no output schema, additional context about the output format would be beneficial.

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 coverage is 100% with a single optional parameter. The description's parameter mention is implicit ('app_path' inferred from 'remote directory'), but adds no new semantics beyond what the schema already provides.

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 ('inspects') and resource ('remote project structure via SSH'), and lists a comprehensive set of detected items (lockfiles, package managers, etc.), clearly distinguishing it from sibling tools like 'inspect_server' which likely have different scopes.

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 explicit guidance on when to use this tool versus its siblings (e.g., 'inspect_server' or 'verify_health'). It lacks context on prerequisites, when not to use, or which alternatives to consider for specific scenarios.

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