topology_check

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

No annotations are provided, so the description must fully disclose behavior. It states the tool 'reads the topology dataset and returns validation metadata,' but does not clarify that ValidateTopology may also write error features or require specific privileges. This omission could lead to incorrect assumptions about side effects.

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 three concise sentences: purpose, usage context, and output handling. Every sentence adds value without repetition, and the most important information is front-loaded.

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 complexity and the absence of annotations, the description covers purpose, usage scenarios, and post-validation steps (inspect error feature classes in ArcGIS Pro). With an output schema available, the description does not need to detail return values, but it omits prerequisites like ArcPy license or path constraints already in schema.

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 input schema already provides detailed descriptions for both parameters (in_topology with path constraints, visible_extent with extent options). The tool description adds no additional parameter information, so it does not enhance beyond the schema. With good schema coverage, baseline 3 is appropriate.

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 validates a geodatabase topology using ArcPy ValidateTopology, specifying the verb and resource. It differentiates from sibling tools like check_geometry or repair_geometry by focusing on topology rule validation after editing workflows.

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 to use this tool 'after editing, appending, repair, or geometry cleanup workflows,' providing clear context. It does not, however, mention when not to use it or list alternative tools, so it lacks exclusionary guidance.

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