Update Sameway

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false, and the description is consistent with all of them. It adds real context beyond the annotations: the new version only takes effect on the next start, so the user must restart, and the tool's reply should be relayed verbatim. No contradiction.

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?

Three short sentences, front-loaded with the core action before the install condition and the restart caveat. 'Say what came back word for word' is instruction-flavored but earns its place given there is no output schema to convey response handling.

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 single-boolean tool with annotations covering the safety profile, the description covers the action, the branch behavior, the deferred effect (restart needed), and output relaying. It does not mention network/permission requirements, though openWorldHint=true already signals an external fetch.

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?

There is only one parameter and schema description coverage is 100%, so the schema already fully explains the true/false meaning of 'install'. The description restates that same distinction rather than adding format, default, or edge-case detail, so the 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?

The description names a specific verb and resource: it looks for a new version of the sameway program itself and optionally installs it. It also disambiguates from the many sibling update/record/canvas tools by stating 'Not for content and not for the canvas.' Slightly circular wording ('sameway program itself') keeps it just short of a 5.

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?

It gives an explicit conditional: install=true installs when a version exists, install=false only reports whether one exists, and it names the exclusions (not content, not canvas). No specific sibling is named as the alternative, but the when-to-use and when-not conditions are clear.

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