Chart Info

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds the useful behavioral detail that it reads fields, axes, and display properties, but it does not add auth requirements, rate limits, or failure behavior beyond what the output schema and annotations cover.

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 a single front-loaded sentence that communicates the core action and lookup key without filler. It is appropriately sized for a read-only chart-info tool.

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?

With an output schema present, the description need not detail return values, and annotations cover the safety profile. However, because all five input parameters have 0% schema description coverage, the description is incomplete enough that an agent may not understand how the chart is scoped by project, map, and member context.

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% for five parameters, so the description carries the burden. It only clarifies that title is the unique lookup key and that the chart is a typed ArcPy chart, leaving aprx_path, map_name, member_name, and member_type unexplained in the description or schema.

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 states a specific verb-resource pair: read a typed ArcPy chart's fields, axes, and display properties by unique title. It is clearer than a generic chart-info tool, though it does not explicitly contrast itself with sibling tools such as arcgis_pro_list_charts or arcgis_pro_export_chart.

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 says the chart is identified by unique title, which implies when it might be used, but it gives no explicit when-to-use or when-not-to-use guidance. It also does not point to alternatives for listing, exporting, or modifying charts.

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