get_summary_chart_instructions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says the tool returns instructions and live data, offering no information about read-only status, output format, potential side effects, or what the 'instructions' contain. This is minimal disclosure for a tool with an unspecified behavior profile.

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, short sentence with no wasted words. It is front-loaded with the core action and resource. It could be more informative, but it is concise and structurally appropriate for a zero-parameter 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?

For a tool with no output schema and no annotations, the description is too vague to be complete. It fails to specify what the 'instructions' are, what 'live data' refers to, what chart is summarized, or what an agent should expect when invoking it. A zero-parameter tool still needs enough context for the returned data to be interpretable.

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 has zero parameters, and a zero-parameter tool sets a baseline of 4 because there is nothing for the description to clarify. The description does not mention parameters, but none exist, so this is not a gap.

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 clear verb and resource: it returns instructions and live data for a summary chart. It is distinguishable from sibling tools like get_arcgis_map_instructions and get_maplibre_map_instructions, which are map-focused, and from the other summary tools that return specific data sets. However, it does not elaborate on what kind of summary chart is meant, leaving some ambiguity.

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?

There is no guidance about when to use this tool versus any alternative. The description does not mention contexts, exclusions, or how this relates to sibling tools such as get_summary_transmission_lines or get_arcgis_map_instructions. An agent receives no decision support for tool selection.

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