get_subdomains

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only mentions enumeration from CT logs and uniqueness, but does not disclose pagination behavior, rate limits, response size, or whether results are sorted. The presence of page and limit parameters is not addressed in the description.

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, focused sentence that immediately conveys the tool's purpose. No extraneous words or repetition. It is efficiently front-loaded and easy to parse.

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?

Given the absence of annotations and the presence of three parameters with pagination defaults, the description is too brief. It does not cover pagination, result ordering, or what 'unique' means in practice. The tool has an output schema, but without its content, the description remains incomplete for safe 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?

Schema description coverage is 0% and the description does not explain any parameters. While parameter names (page, limit, domain) are self-evident, the description adds no additional meaning about their format, constraints, or interaction. For a tool with low schema coverage, this is insufficient.

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 'Enumerate unique subdomains seen in CT logs', which is a specific verb (enumerate) and resource (unique subdomains from CT logs). This effectively distinguishes it from sibling tools that focus on certificates (e.g., get_certificate, get_domain_certificates).

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 description provides no guidance on when to use this tool versus alternatives. It does not specify prerequisites, typical scenarios, or when not to use it. Without any usage context, the agent cannot make an informed choice among siblings.

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