Url Tls

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

Discloses that the tool inspects certificates, does not execute JS, and has caching behavior. Annotations already provide read-only and idempotent hints; description adds behavioral context without contradiction.

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?

Compact, front-loaded with purpose, no unnecessary words. Every sentence adds value.

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 presence of an output schema and annotations, the description covers purpose, parameter guidance, constraints, and caching behavior sufficiently for an agent.

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%, and the description reinforces parameter usage: url must be absolute public HTTP(S), fresh controls caching. Adds value by clarifying when to use fresh=true.

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 inspects public HTTPS certificates on port 443, using a specific verb and resource. It distinguishes itself from sibling tools that focus on other URL aspects like status, headers, or redirects.

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?

Provides clear context: use only for public HTTP(S) resources, does not execute JavaScript or bypass access controls, and explains when to set fresh=true vs false. However, lacks explicit alternatives or when-not-to-use compared to siblings.

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