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

The hard-coded ':443' and 'certificate-pinning' add a real behavioral constraint beyond the tool name. With no annotations, though, the description doesn't state that this performs a DNS/TLSA lookup, how the query input is processed, or how empty or invalid queries behave.

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 extremely concise and front-loaded with the acronym and its specialized meaning. It contains no filler, though its brevity is partly responsible for the missing parameter and usage guidance gaps.

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 operation is simple and an output schema exists, so return-shape information is presumably covered elsewhere. Still, with no annotations, no parameter explanation, and no usage context, the one-line description is only minimally complete for confident invocation.

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 single 'q' parameter has no schema description (0% coverage), and the tool description never explains that q is a domain name, hostname, or how it should be formatted. The DANE/TLSA context weakly implies the meaning, but the agent is left guessing.

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 identifies the resource as DANE/TLSA certificate-pinning records and narrows the scope to port 443, so the basic purpose is evident. However, it is phrased as a noun fragment rather than an explicit action verb, and it doesn't directly contrast itself with siblings like tls or tlsscan.

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?

No guidance is given about when to use this tool versus alternatives such as tls, tlsscan, dns, or dnssec. There are no exclusions, prerequisites, or examples to help route the agent correctly.

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