mcdev_component_checklist

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

No annotations exist, so the description carries the burden. It does disclose the return content (a checklist of questions plus dependent metadata types), which is the key behavioral fact and useful given there is no output schema. However, it says nothing about whether component keys are validated, what happens on an unknown key, or how dependency resolution is performed.

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?

A single sentence with the verb front-loaded and zero filler. Nothing could be removed without losing information.

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 one-parameter read tool with full schema coverage, the description is nearly sufficient, and it partly compensates for the absent output schema by characterizing the return value. It stops short of telling the agent how to discover valid component keys, which is relevant given the sibling list.

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% and the single `component` parameter is well documented, so the baseline is 3. The parenthetical examples ("journey, automation") merely repeat the schema's own examples and add no new semantics.

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?

Names a specific verb ("Return") and a concrete resource ("structured checklist of questions and dependent metadata types"), scoped to authoring/migrating SFMC components. It does not explicitly distinguish itself from siblings like mcdev_list_metadata_types, which also deals with metadata types, so an agent must infer the boundary.

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 phrase "for authoring or migrating SFMC components" gives an implicit usage context, but there is no statement of when NOT to use it and no named alternative (e.g. use mcdev_list_metadata_types to enumerate valid keys). The agent is left to infer.

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