Inspect stored original application colors

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds useful context: it reports stored rather than live colors, and warns that GDF color bits and custom previews cannot prove native display — genuine evidence caveats beyond 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?

Four dense sentences, front-loaded with the core action before the caveats and verification guidance. Every sentence carries information, though the domain jargon ('native Symbol Pinstub Names') makes it slightly heavy for the tool's simple one-parameter nature.

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 read-only inspect tool with annotations carrying safety and no output schema, the description covers purpose, scope, evidence limitations, and verification alternatives. It hints at the grouped role output without detailing return format, which is a minor gap given no output schema exists.

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 100% for the single optional 'root' parameter, which already documents that invalid explicit roots are refused. The description adds nothing further about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource: 'Read only the [Colors] section of installed maxplus2.ini.' It also delimits scope precisely (the Colors section only) and clarifies the roles it separates, so an agent can tell it apart from other inspect tools like gdf_inspect or scf_inspect.

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?

It sets an explicit boundary ('Reports stored preferences, not live unsaved colors') and routes the agent to alternatives ('Verify visible colors using original Color Palette Preview and desktop_observe'). Clear selection context, though the routing is somewhat indirect and one named resource isn't a sibling tool.

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