pbs_acme_directories

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

Description says 'No params,' but the input schema includes an optional proximo_target parameter. This contradiction misleads agents about required invocation. Beyond that, it discloses read-only nature and config dependency.

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?

Very short and front-loaded, but the inaccuracy about parameters undermines its effectiveness. Conciseness is not helpful if incorrect.

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?

Covers config requirement and read-only nature, but misses documenting the optional proximo_target parameter. Output schema exists, so return values need no explanation. Overall adequate but incomplete.

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?

Despite schema covering 100% of parameter description, the description incorrectly states 'No params,' providing no added meaning and contradicting the schema, which harms semantic understanding.

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?

Clearly states it lists PBS's built-in ACME CA directory endpoints, specifying the resource and verb. Disambiguates from sibling ACME tools by focusing on directory listing.

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: READ-ONLY, needs PROXIMO_PBS_* config. Lacks explicit when-to-use vs alternatives, but the tool is self-explanatory among siblings.

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