help

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

With no annotations, the description carries the full burden. It discloses the tool is deprecated, which is a significant behavioral trait, but it does not describe what happens on invocation, output, or side effects. Still, the deprecation warning is valuable.

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, front-loaded sentence with no wasted words. It communicates the essential redirect immediately.

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 the deprecation and the clear pointer to `stata_help`, the description is sufficient to route the agent away from this tool. It does not explain parameters or return values, but for a deprecated tool, the recommended action is to avoid it, so the context is mostly complete.

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 schema has 2 parameters with no descriptions, and the description offers no parameter guidance whatsoever. The agent cannot infer the meaning of `command` or `project_path`.

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 does not state what the tool does; it only provides a deprecation notice and points to an alternative. It lacks a verb and resource, and while it distinguishes from siblings by naming stata_help, it doesn't explain its own purpose.

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 explicitly says 'Deprecated: use stata_help,' clearly telling the agent when not to use this tool (always) and which alternative to use.

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