cg_installed

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

No annotations provided, so description carries full burden. It states 'mutate' but doesn't disclose side effects, reversibility, error handling, or authorization needs for actions like upgrade/uninstall. Adequate but not thorough.

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 and a short instruction. Front-loaded with purpose. Somewhat mixed content (usage guidelines and parameter mappings in same sentence) but still efficient and clear.

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 mutation tool with 3 params and no output schema, description covers purpose, usage context, and action-specific requirements. However, lacks information on return values, error states, or operation results. Slight gaps given complexity.

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%, but description adds value by linking parameters to actions (e.g., upgrade requires widget_dir and optionally version). This clarifies usage beyond the schema's static descriptions.

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 clearly states the verb 'Mutate' and resource 'widgets already installed in the current project', distinguishing it from sibling tool cg_registry install for adding new widgets.

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?

Explicitly says when to use this tool (installed copies only) vs cg_registry install for adding new widgets, and details action-specific requirements: upgrade needs widget_dir/version, uninstall needs widget_dir.

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