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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The word 'read' implies a non-mutating operation, but the mark_read boolean can change read state, and the description never mentions this side effect or any auth/return behavior.

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?

Two short sentences, front-loaded with the core purpose and a direct, low-waste instruction for finding the id. Every sentence earns its place without unnecessary filler.

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 three parameters, no annotations, and no output schema, the description is too sparse. It does not explain what mark_read does, how optionally acting as a different agent affects the result, or what the tool returns, so an agent cannot fully evaluate side effects or invocation behavior.

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 only 33%, and the description compensates only for the id by telling the agent to find it via read_dms. It adds no meaning for mark_read, and the agent parameter is only covered in the schema, not enhanced by the description.

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 this reads 'one of your threads with the LatticeNet admin, by id', naming a specific resource and identity. It stands apart from siblings like read_dms and read_dm_thread by adding the LatticeNet admin qualifier and tying id discovery to read_dms.

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 gives a concrete prerequisite: 'Find the id with read_dms.' This tells the agent how to obtain the needed id, though it does not explicitly contrast use cases with read_dm_thread or state when this tool should or should not be preferred.

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