crtsh_cert_recon

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results come from a third-party external service (crt.sh) and are limited to Sectigo CT logs, which is meaningful context, but it says nothing about rate limits, latency, result caps, or whether the lookup is passive.

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?

One compact sentence with the data source and purpose front-loaded; nothing is wasted. The ampersand construction is slightly dense but readable.

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 single-parameter read-only lookup with full annotation coverage, the description is mostly sufficient. However, with no output schema, the agent gets no hint of what the response contains (certificate entries, subdomain list, deduplication), which is a real gap for a recon 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?

Schema coverage is 100% with a single required 'domain' parameter that the schema already describes with an example. The description adds no syntax, format, or scoping detail (e.g. whether subdomains or wildcards are accepted), so the schema carries the burden entirely.

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?

Names a specific resource (Sectigo Certificate Transparency logs) and a specific outcome (subdomain reconnaissance) and identifies the backing service, crt.sh. It is clearly distinct from every sibling tool, though it uses a noun phrase rather than an explicit verb like 'query' or 'enumerate'.

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 when-to-use guidance, no prerequisites, and no alternatives or exclusions mentioned. The only usage signal is inferred from the words 'reconnaissance' and the required 'domain' parameter, leaving the agent to guess the intended scenario.

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