Get control model (structure + node types)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, indicating safety. The description adds behavioral context by noting it returns default/reset values and that payload keys must come from this call. No contradiction with 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?

Two sentences: first gives purpose and detailed output, second gives usage guidance and a parameter hint. No unnecessary words, front-loaded with key 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?

Despite no output schema, the description fully describes the return structure (subCompositions with fields). All 4 parameters are documented in schema, and the description adds context for their use. Siblings are addressed via usage guidance differentiating it as a discovery call.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that the returned control-node ids should be used as keys for writing content, and provides the full return structure, which is not in the schema.

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 specifies 'Get the structural model of an app: every sub-composition and its control nodes with id, title, type, default/reset values, and index.' It clearly states the verb, resource, and output, distinguishing it from siblings by emphasizing it as a schema-discovery call to run before writing content.

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?

Explicitly states 'run BEFORE writing content — payload keys must be control-node ids from here.' This provides clear when-to-use guidance and implies not to use when you already have the schema. It also mentions optional filtering via sub_composition.

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