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

With no annotations, the description carries the full burden of explaining behavior, but it only states what MTA-STS is, not what the tool does with it (e.g., whether it performs a DNS lookup, validates a policy, or fetches a file). No side effects, network behavior, or output expectations are disclosed.

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 text is short, but this is under-specification rather than conciseness. A single noun-phrase does not earn its place because it omits the essential verb and parameter guidance needed for correct tool use.

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?

Despite having an output schema, the description is too incomplete to support correct invocation. It does not state what input triggers a result, what kind of result is returned, or how the tool relates to the surrounding MTA-STS toolset. This is inadequate even for a one-parameter tool.

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 one parameter, q, with no description coverage (0%), and the description does not explain what q means or how to format it. Since the schema provides no help and the description is silent, the agent cannot infer valid input values.

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 expands the acronym and names the subject area ('MTA-STS', 'Inbound-mail TLS enforcement policy'), so it identifies the topic, but it lacks any action verb or outcome such as 'query', 'fetch', or 'check'. It does not distinguish this tool from siblings like tls, tlsscan, or dns, leaving the agent unsure what operations it actually performs.

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?

There is no guidance on when to use this tool versus related tools like dns, tlsa, or hstspreload. No context, prerequisites, or alternative routing is provided, so the agent cannot decide if this is the right tool for a given MTA-STS lookup task.

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