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

Annotations already establish that this is a safe, read-only, non-destructive operation. The description adds that it returns one tracked asset with recent check history, but does not explain returned fields, history depth, or any failure 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?

The description is a single front-loaded sentence with no wasted wording. It immediately states scope and the inclusion of recent check history.

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 simple read-only tool with annotations covering safety, the description gives the basic scope and return hint. However, because there is no output schema and no id documentation, an agent still lacks enough detail about the identifier and the shape of the returned asset/history.

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?

There is one parameter with 0% schema description coverage, so the description must carry the burden of explaining it. 'By id' identifies the selector, but it does not clarify what kind of id is expected, its format, or whether it is an asset id versus a domain or certificate identifier.

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 resource ('tracked domain or certificate') and retrieval by id, and adds that recent check history is included. It is clear enough to distinguish from list_assets, though it does not explicitly contrast with get_asset_history or lookup_domain.

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 phrase 'by id' implies the usage condition for retrieving one asset, but there is no explicit when-to-use guidance versus alternatives such as get_asset_history, lookup_domain, or lookup_cert. The implied use case is adequate but not fully disambiguated.

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