execute_python

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

With no annotations, the description carries the full burden of disclosure. It explains the execution environment (available variables), how to return data via the result variable, and how stdout is captured, which is substantial. It does not mention potential side effects or limitations, but the arbitrary-code nature is openly stated.

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 efficient: a one-line purpose, a brief usage directive, a compact list of available variables, and a short example. Every sentence contributes functional information without repetition or 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 general-purpose code execution tool, the description covers all essential operational details: input format, environment, output mechanism, and a concrete example. The presence of an output schema further reduces the need to spell out return structures, so nothing critical is missing.

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 schema only names the 'code' parameter with no description, so the description adds essential meaning. It defines the parameter as executable arcpy/Python code, lists the pre-defined variables, explains the result variable convention, and gives a complete usage example.

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 executes arbitrary Python/arcpy code within the ArcGIS Pro bridge, with a specific verb and resource. It also distinguishes itself from sibling tools by framing this as a fallback for operations not covered by more specialized tools.

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 for complex arcpy.mp operations not covered by other tools, which sets a clear boundary. It does not name specific alternative tools, but the exclusion is unambiguous, and the provided example reinforces practical usage.

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