create_workspace_rule

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

With no annotations, the description carries the full burden. It usefully discloses where files are written (.agents/rules/*.md or GEMINI.md), which is real behavioral context, but says nothing about overwrite behavior, collision with existing rules, or required permissions for global scope.

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 that identifies the action, the resource, and the write destinations with no filler.

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 4-parameter mutation tool with no annotations and no output schema, the description covers the 'what' and 'where' but omits overwrite semantics and what a successful call produces. Adequate but with a clear gap for a file-creating operation.

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% and both enums (scope, trigger) are documented in the schema itself. The description only echoes the file targets already implied by the filename examples, adding no new parameter meaning.

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?

Specific verb ('Creates') plus a well-defined resource ('an Antigravity rule') and concrete write targets (.agents/rules/*.md or GEMINI.md). It is distinguishable from siblings like list_rules/get_rule, though it does not explicitly contrast itself with create_workspace_skill.

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?

No when-to-use guidance, no conditions for choosing between workspace vs global, and no mention of an alternative tool. The scope enum in the schema conveys the choice mechanically, but the description offers no decision context.

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