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

The annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Read' is consistent with them. The description adds useful context about output organization and field attributes, but it does not disclose operational behavior such as auth requirements, failure modes, or what happens if the automation_id does not exist. With annotations covering the safety profile, this is adequate but not especially rich.

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 single sentence is front-loaded with the primary action and resource, then adds precisely the details that matter for selecting and using the tool: grouping, ordering, and returned field attributes. There is no filler or redundant repetition of the title or schema.

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 no output schema, the description does the necessary work of explaining what the response contains: config fields grouped by section, with current value, default, and fill provenance. It is nearly complete for a simple one-parameter read-only tool, though 'fill provenance' is left as domain jargon and error/not-found behavior is not addressed.

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 documents automation_id with type, format, pattern, and a description, so schema description coverage is 100%. The tool description adds no parameter-level meaning beyond referring to 'an automation,' but the schema already carries the full burden, so the baseline of 3 is appropriate.

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 uses a specific verb ('Read') and a specific resource ('an automation's module config fields (its Policy)'), and it clarifies the response contents: grouped by section, with current value, default, and fill provenance. It is clear, though it does not explicitly differentiate itself from sibling getAutomation/listAutomations tools beyond naming the config-fields resource.

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 implies the tool is used when you need an automation's module config fields or Policy, but it provides no explicit when-to-use guidance, alternatives, or exclusions. Among many getAutomation/getAutomationCurrent/listAutomations siblings, an agent must infer the right choice from the resource term alone.

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