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

The annotation suite (readOnlyHint: true, destructiveHint: false) already provides strong behavioral guarantees. The description adds minimal value by confirming it is a 'Read' operation, which is redundant but confirms the non-mutating nature of the tool.

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 tool definition is highly concise. The single sentence is direct, efficient, and contains zero unnecessary words, maximizing the information density.

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?

Given the simplicity of the schema (one ID), the description provides just enough information to identify the tool's function. However, since it has 0% parameter description coverage, the description lacks any deeper explanatory context about the required input.

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%, requiring the description to add semantic value. However, it merely identifies the resource ('contact') but fails to provide context on the required parameter ('contactId') beyond its role in accessing the configuration.

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 uses specific language—'Read a contact's site/category access configuration'—which immediately identifies the resource and the exact type of configuration being retrieved. It distinguishes itself well from generic list or export tools in the sibling set by focusing on a specific access setting.

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 description provides no guidance on when to use this tool versus alternatives. It makes no mention of prerequisites or scenarios where another tool in the large sibling list would be more appropriate for the user's goal.

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