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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered without the text. The description adds real domain detail beyond that, notably that the name and details block always comes first regardless of configuration, plus which sections the layout covers. It stops short of describing the shape of the returned data, which matters because there is no output schema.

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 front-loaded sentence anchored by the 'Settings → Contact panel' path, with no filler. The nested parenthetical about name and details coming first is slightly awkward to parse but carries genuinely useful 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 zero-parameter, read-only settings tool with complete annotations, the description covers what configuration is exposed and enumerates its parts. Since no output schema exists, a sentence sketching the returned structure would fully close the gap, but an agent has enough to call it correctly.

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 tool takes no parameters, so there is no parameter meaning for the description to convey; the baseline for a zero-parameter tool applies. The description correctly implies the scope is fixed to the current workspace's contact panel with no filtering options.

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 the specific resource (the Contact panel layout under Settings) and enumerates its components: blocks, order, Stripe rows, pinned fields, header badges, and pinnable contact fields. That enumeration makes it clearly distinguishable from the sibling update_contact_panel. It lacks an explicit verb phrase like 'Returns the layout', so the read action is inferred rather than stated.

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?

There is no statement of when to call this versus update_contact_panel, and no prerequisite or workflow guidance (e.g. 'call before updating to see current order'). The 'Settings → Contact panel' breadcrumb only locates the feature, it does not tell the agent when the tool applies.

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