contrastapi

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

No annotations are provided, and the description carries no behavioral information. It does not disclose what data is returned (certificate chains, issuer info, timestamps), whether the operation is read-only, or any rate limiting considerations.

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?

While brief (single word), this represents under-specification rather than effective conciseness. No information is front-loaded because no actionable information is present.

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 tool without output schema, the description is still inadequate. It fails to explain the CT log data scope, return format, or how results are aggregated, leaving critical gaps in understanding.

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?

With 0% schema description coverage (the 'domain' parameter has an empty description), the description fails to compensate by explaining what the domain parameter represents or its expected format. The word 'Certs' adds no semantic value regarding the input parameter.

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 'Certs' identifies the resource type (certificates) but fails to specify the action (fetch, search, list) or scope. Given the tool name 'ct_logs', it implies Certificate Transparency logs, but lacks the verb and specificity needed to distinguish it from sibling tools like domain_report or dns_records.

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 provided on when to use this tool versus alternatives like domain_report or dns_records. No prerequisites, filtering options, or exclusions mentioned.

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