stellar_cache_path

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

No annotations are provided, so the description carries the burden, but 'Show' reasonably conveys a read-only, non-destructive lookup. It does not say whether the directory must already exist, whether the path is created, or what the returned value looks like, though for a trivial zero-param getter these gaps are minor.

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?

A single front-loaded sentence with no filler, perfectly sized for a trivial informational tool. 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?

With no output schema, the description does state the essential return value (the cache directory location), and there are no parameters or annotations requiring disclosure. It is nearly complete for a tool this simple, with only the ambiguity around directory existence/creation left open.

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?

The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly introduces no parameter concepts that would need further explanation.

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 (Show) and resource (the cache directory's location), so an agent can tell what it does without opening the schema. It doesn't explicitly distinguish itself from the parallel sibling stellar_config_dir, but the resource name is distinct enough to differentiate in practice.

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?

Usage is implied rather than stated: a zero-parameter informational getter is self-evidently used to retrieve the cache path. There is no explicit when/when-not guidance and no mention of the nearby alternatives (stellar_config_dir, stellar_cache_clean, stellar_cache_actionlog_list).

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