compact_gdb

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

With no annotations, the description carries full burden. It discloses that the tool 'mutates the geodatabase storage layout but not feature content', clearly indicating a non-destructive mutation. It does not cover auth needs or rate limits, but for a geodatabase maintenance tool, this is adequate.

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 concise with three sentences that front-load the main action and context. It avoids fluff but could be more structured by separating usage and behavior into clearer sections.

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 tool's simplicity (one parameter, output schema present), the description covers purpose, usage scenario, and key behavioral trait. Explanation of return values is unnecessary due to the output schema, resulting in adequate completeness.

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?

Despite the schema having a description for the 'gdb' parameter, the context signal indicates 0% schema description coverage. The tool description does not add any extra meaning beyond the parameter name, failing to compensate for the low coverage. It merely restates the purpose without clarifying parameter details.

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 tool compacts a file geodatabase using ArcPy Compact, with specific verbs and resource. It differs from siblings like 'create_file_gdb' or 'delete_dataset', making its purpose distinct and unambiguous.

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 provides clear context for when to use the tool: 'as maintenance after heavy editing, deletion, or intermediate output cleanup'. It implies when it is appropriate but does not explicitly mention when not to use it or list alternative tools, which prevents a higher score.

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