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

With no annotations provided, the description carries the behavioral disclosure burden. It communicates that the tool is a read-oriented browse operation and that the output consists of normalized records with confidence levels. It does not mention pagination behavior, sort defaults, authorization requirements, or what happens when filters return no results, but for a browse tool this is a minimally acceptable disclosure.

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 three sentences with no filler. The main purpose is front-loaded, the output nature is stated, and the key filtering capabilities are summarized efficiently. Every sentence earns its place.

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?

The description covers the core browsing and filtering behavior but omits several operational details that matter given the 9 parameters and no output schema: pagination defaults, sort options, and the shape of returned records beyond 'normalized.' It is sufficient for a simple call, but an agent would still need to rely on the schema for complete invocation 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 100%, so the baseline is 3. The description adds value by grouping parameters into meaningful filter categories, clarifying that 'linked' refers to having a project_id, and explaining the practical meaning of expiringWithinDays. This goes beyond the schema alone without duplicating 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 states a clear verb and resource: 'Browse LTS records from DHSUD with filters.' It further explains what the records contain (normalized records with confidence levels) and lists the main filter dimensions. It does not explicitly contrast itself with siblings like lts_search or lts_by_region, so it stops short of full differentiation.

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 clearly identifies the general use case: browsing and filtering LTS records, and even gives a specific pointer for expiringWithinDays. However, it never mentions when to prefer a sibling tool such as lts_search or lts_stats, nor does it state when not to use lts_records. Usage context is implied rather than explicitly contrasted.

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