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

Annotations already declare this as read-only and non-destructive, so the description doesn't need to repeat that. The added value is the disclosure that the content is 'untrusted reference data' and the caution that it should not be used to execute code or contact anyone, which is useful behavioral context for security-conscious agents. However, it doesn't describe the return format or any error behaviors, which is acceptable given annotations cover safety, but it could add more on response shape.

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 two sentences and front-loads the core purpose (read current selected content) before the caution about untrusted data. Every sentence earns its place; the security note is a meaningful addition, and there's no fluff. It could be more structured, but it's concise and efficient.

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 tool's simplicity (one parameter) and the annotations covering read-only safety, the description provides the essential safety context (untrusted data) and mentions the integrity metadata (revision, SHA-256), but it doesn't clarify whether the output includes the raw content or just metadata, nor does it explain the significance of the resource_id pattern. It's adequate for a basic read tool but leaves some gaps about output and usage context.

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%, so the description must compensate for the parameter, but it doesn't provide any additional meaning about resource_id beyond what the schema shows (pattern and format). The pattern itself is documented in the schema, so the description adds no new semantics like 'the identifier of the resource you want to read' — it's implicit. Baseline is 3 because schema has full pattern info, but the description doesn't enhance it.

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 clearly states the verb 'Read' and the resource 'selected content of a TrustVerum resource', and mentions revision and SHA-256 as key attributes. It is distinguishable from siblings—list_resources and access_policy—by the focus on reading a specific resource's content with integrity metadata, though it doesn't explicitly name the siblings.

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 implies that this tool is for reading the current selected content of a resource with revision and SHA-256, but it doesn't explicitly state when to use this vs. the sibling tools. It gives no context on when to use list_resources (e.g., to enumerate resources) or access_policy (e.g., to check permissions). Some guidance is implied but not direct.

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