Resolve a path with environment variables

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that expansion happens 'via the SSH session', which implies a session must be active and that resolution is remote rather than local. It doesn't detail failure modes (e.g., undefined variables), but the annotations carry the main behavioral burden.

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, no filler. The core action is stated first, and the mechanism ('via the SSH session') is added in the second sentence. Every word earns its place.

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 simple 2-parameter read-only tool with strong annotations, the description is mostly complete. It lacks details on edge cases like undefined environment variables or whether the resolved path is returned as a string, but the output schema is absent and the description could have added a bit more about the return value. Still, the tool is simple enough that the current description is adequate.

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 compensate. It explains what happens to the 'path' parameter (expansion of env vars and ~), but it does not explain the 'sessionId' parameter beyond the implicit SSH session context. The description adds some meaning for 'path' but leaves 'sessionId' semantics to be inferred from the name.

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 a specific verb ('Resolve') and resource ('a path with environment variables'), and clarifies it expands environment variables and ~ via the SSH session. It is clear about what the tool does, though it doesn't explicitly distinguish it from sibling file tools; the unique 'resolve path' action is enough to differentiate.

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 implies usage: use this when you need to expand environment variables or ~ in a path over an SSH session. It does not explicitly state when not to use it or name alternatives, but the context of needing path resolution is reasonably clear.

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