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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds almost nothing beyond that: no return shape, no pagination, no note on what a 'saved layout' contains or what happens when no layout is saved. With annotations doing the heavy lifting, the description still leaves behavioral questions unanswered.

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 short sentences, front-loaded with the core action and followed by the key constraint. No filler, no repetition of the title.

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 tool with no output schema, the description should at least characterize the return value (a layout structure of fields/sections) so an agent knows how to consume it. It also doesn't say what happens for an entity/view combo with no saved layout. Annotations cover safety, but the read-side behavior remains underspecified.

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 0%, and there is a nested object with two required parameters. The description partially compensates by mapping 'entity' and 'view' to the parameters, but it doesn't clarify enum semantics (e.g., which views apply to which entity) or what 'discovered field IDs' means in relation to these params. Adequate but with clear gaps given zero schema documentation.

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 names a specific verb and resource: 'Read the saved page layout for an entity and view.' That is clearly distinguishable from sibling 'read/list' tools covering other resources. It doesn't differentiate itself from nearby layout-adjacent tools like get_flow_field_catalog or get_flow_template, but the resource is specific enough to route correctly.

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?

'Use only discovered field IDs' implies a prerequisite workflow (field discovery must happen first), which is useful directional guidance. However, it doesn't say when to call this versus get_flow_field_catalog/get_flow_template, nor does it state where discovered IDs come from. Usage context is implied rather than stated.

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