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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'fingerprint check', implying analysis, but does not mention whether it is read-only, what it returns, rate limits, or side effects. The description is too terse to convey the tool's behavior beyond the basic purpose.

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 sentence with no wasted words, but it is under-specified. It conveys the core purpose efficiently but omits essential usage details. The structure is flat and lacks separation of purpose, input, and output, making it minimally acceptable but not well-organized.

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 tool has one parameter, but with zero schema description and no annotation, the description must explain the input and usage. It only states the purpose, leaving the agent without knowledge of what to pass as 'q'. Even though an output schema exists, the input side is incomplete, so the tool cannot be called correctly without further information.

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 input schema has one parameter 'q' with no description, and the schema description coverage is 0%. The tool description does not explain what 'q' represents or how to format it. An agent cannot infer that 'q' likely expects a domain or subdomain to check. The description fails to compensate for the missing schema details.

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 the tool's function: checking for subdomain takeover via dangling CNAME records. It uses a specific verb ('check') and resource ('Subdomain Takeover') and distinguishes it from sibling tools like 'subdomains' or 'dns' by focusing on a vulnerability fingerprint. However, it could be more explicit about the action, but it's adequate.

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 provided on when to use this tool versus alternatives. The description does not explain what input to provide (what 'q' should contain), when to call it, or how it relates to similar security tools. An agent has no context to decide if this is the right tool for a given task.

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