pbs_acme_tos

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

With no annotations, description fully discloses: read-only, live HTTPS fetch, validated, response tainted as adversarial, and requires PROXIMO_PBS_* config. This goes beyond basic expectations.

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?

Description is compact but packs essential information. A single sentence with semicolons could be clearer, but it is not overly verbose and front-loads the purpose.

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 schema coverage, output schema existence, and low complexity, description covers all needed aspects: input parameters, behavior, security implications, and config requirements.

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 description adds value by explaining the default behavior for 'directory' (omit to use PBS's default CA) and the purpose of 'proximo_target' (target selection).

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?

Description clearly states 'READ-ONLY: get the Terms-of-Service URL for an ACME directory (or None if the CA advertises no ToS).' This uses a specific verb (get) and resource (Terms-of-Service URL), and distinguishes from sibling ACME tools like pbs_acme_account_create.

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?

Description implies usage for fetching ToS from an ACME directory, and notes it is read-only and fetches live. It does not explicitly state when not to use or mention alternatives, but the context is clear enough for an AI agent.

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