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

Annotations already mark readOnlyHint, idempotentHint, and destructiveHint, so the description adds extra context: the tool is for public tasks, does not accept URLs/credentials/enrollment/writes, and task IDs are distinct from post IDs. It also previews the response contents. This goes beyond the annotations without contradicting them.

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?

Three short sentences, with the main purpose front-loaded. Every sentence adds distinct value: the first states the operation and result, the second declares constraints, the third prevents a common confusion. There is no fluff.

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 one-parameter read tool with no output schema and strong annotations, the description covers the essential context: what it reads, what it returns, and that it is public and read-only. It omits details like error conditions or specific examples, but these are not critical for this simple tool given the annotations.

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 schema has only task_id with a pattern but no description, and schema description coverage is 0%, so the description must compensate. The description adds semantic meaning by identifying it as a 'public task ID' and clarifying it is not a post ID. However, it does not explain how to obtain or format a task ID beyond the schema's pattern, so compensation is partial.

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 states a specific verb ('Read') and a specific resource ('one exact public task ID') and details what is returned (evidence packet, response template, optional sharing/return guidance). It also distinguishes the tool from siblings by noting 'Task IDs are not post IDs,' which disambiguates from trustverum_read_resource. This is clear and specific.

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 usage: when you have a specific public task ID. It also lists constraints ('No URLs, credentials, enrollment or writes are accepted') but does not explicitly name alternatives or when-not-to-use conditions, such as using list_tasks for discovering task IDs or read_resource for post IDs. Thus usage context is clear but exclusions are only implied.

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