execute_arcpy_code

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

No annotations exist, so the description carries full burden. It only mentions outputs (stdout, stderr, exceptions) but omits critical behavioral traits: arbitrary code execution risks, side effects on data, environment isolation, or authentication requirements. This is a significant gap for a code execution tool.

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?

Single sentence effectively conveys the core purpose. Could be improved by front-loading the return values, but overall concise and no redundant information.

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?

Despite an existing output schema (not shown), the description lacks depth regarding runtime environment, security precautions, resource limits, and detailed return structure. For a powerful execution tool, this is incomplete.

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?

Parameter schema has 0% description coverage and description adds no explanation beyond parameter names. Parameters like 'workspace', 'project_path', and 'open_current_project' remain semantically opaque. For a 5-parameter tool with no schema descriptions, the description fails to compensate.

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 ArcPy code in the ArcGIS Pro environment and returns stdout, stderr, and exceptions. It uniquely identifies this tool as code execution, distinct from sibling GIS operation 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?

No guidance on when to use this tool versus alternatives, no prerequisites mentioned, and no scenarios where use is not recommended. This lack of context leaves the agent without decision-making support.

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