adg_summary

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

Annotations already mark this as readOnlyHint=true. The description adds important behavioral context: the tool operates offline on saved files, not on a running Live instance. It also details the output fields, helping the agent understand return behavior.

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 concise: three sentences front-loaded with the core purpose, followed by a list of output fields and a brief parameter explanation. Every sentence serves a purpose without waste.

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?

The description covers purpose, parameter meaning, output content, and a key usage constraint (offline). It lacks error handling or format details (e.g., path encoding) but is adequate for a single-parameter tool with an output schema.

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 has 0% description coverage, but the description explains the 'path' parameter as 'a filesystem path to a .adg or .adv file'. This adds meaning beyond the raw type (string) and clarifies acceptable file formats. No additional constraints are given, but the explanation suffices.

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's purpose: 'Summarize a saved .adg rack or .adv device preset WITHOUT Live running'. It lists specific output fields (name, rack type, etc.), making the function unambiguous. The verb 'summarize' and resource 'adg/adv preset' are specific, and the 'WITHOUT Live running' distinguishes it from sibling tools that may require Live.

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 states the tool works 'WITHOUT Live running', which is a key usage condition. It does not mention alternatives or when not to use it, but the context is clear: for offline summary of preset files.

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