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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds organization scoping and approval context, including that MCP approval requirements are administrable and business workflow approvals always apply, which is useful behavioral information beyond the 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?

The description is short and has no filler, but the actual action appears in the second sentence after a generic "Use this when..." opener. The approval sentence is relevant but somewhat boilerplate.

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 single-record read with an output schema and rich read-only annotations, the description covers the essential scope: organization context, lookup by ID, and approval considerations. It does not add return-value details, but the output schema already handles that.

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%, but the single parameter is named `id` and the description says "Read a site by ID," which tells the agent the parameter identifies the site. The schema itself supplies the UUID type and pattern, so the description does not need to repeat those details.

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 second sentence states a specific verb and resource: "Read a site by ID." This clearly distinguishes the tool from list_sites and update_site in practice, though it does not explicitly name any sibling as an alternative.

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 this when working with RetailHardHat sites records in the connected organization" gives only a broad usage context. The "by ID" phrasing implies use when an ID is available, but there is no explicit when-not guidance or named alternative such as list_sites.

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