get_pacer_credentials

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: password is not returned on check, validate tests without storing, and delete removes stored credentials. It also implies side effects for set/delete. While it does not cover failure modes or return formats, it provides meaningful behavioral transparency beyond the schema.

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 compact and well-structured. It opens with a one-sentence purpose, then efficiently lists actions in a readable arrow format. Every sentence provides necessary information without redundant filler.

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?

The tool has four distinct actions with different behaviors, and the description covers each sufficiently. It omits explicit return values or error handling, which would be helpful given no output schema, but the core usage and semantics are clear. The prerequisite note about include_live_pacer=true adds important context.

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 75%, and the description adds significant meaning to the action enum by mapping each value to its effect. It also clarifies that pacer_user and pacer_pass are needed for set/validate, matching the schema. However, the 'validate' boolean parameter is not mentioned in the description, though the schema already describes it.

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's purpose: 'Check or update PACER credentials stored in CourtAPI.' It specifies the resource (PACER credentials) and the verb (check/update), and enumerates four distinct actions with their behaviors. This distinguishes it from sibling tools that handle case data retrieval.

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 clear contextual usage: 'PACER credentials are required before any include_live_pacer=true call.' This tells the agent when the tool is needed. It does not explicitly mention alternatives or when not to use it, but the prerequisite context serves as a clear guideline.

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