Gp Mean Center

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the agent already knows this is an idempotent write that produces non-destructive output. The description adds only 'returns verifiable structured results' and a caveat about write/path restrictions, without stating that it creates a new output feature class or its overwrite behavior. It adds marginal context over the annotations.

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 text is short but nearly all of it is filler or name restatement ('meangp mean center', generic service-capability caveat). It is not under-length for the wrong reasons but it fails the 'every sentence earns its place' test because none convey actionable 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?

An output schema exists, so return-value explanation is not required, lowering the bar. However, with four undocumented parameters and no statement of the tool's actual behavior for a GP write operation, the description is not complete enough for an agent to call it correctly.

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 description coverage is 0% and four parameters (in_features, out_feature_class, case_field, weight_field) are entirely undocumented in both schema and description. The description names none of them, so an agent gets no help understanding what case_field or weight_field do.

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 essentially restates the tool name ('ArcGIS Pro: meangp mean center') without explaining what Mean Center actually computes (a geographic/weighted center of input features). An agent cannot distinguish this from sibling GP tools like central_feature or directional_distribution without external knowledge. This is close to a tautology.

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 is given on when to use this tool versus alternatives such as arcgis_pro_gp_central_feature or arcgis_pro_gp_directional_distribution, nor any preconditions or when-not-to-use conditions. The trailing sentence about service capabilities is generic boilerplate that routes nothing.

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