pdm_remote_config_get

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

With no annotations provided, the description must disclose behavioral traits. It does so by noting 'no secrets returned' and indicating a diagnostic category ('DIAGNOSE (LOW)'). This adds useful context beyond the schema, though it could elaborate on error cases or the exact scope of configuration returned.

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 extremely concise—three short lines—and front-loads the core purpose. Every sentence earns its place with no redundant or vague language.

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 that an output schema exists, the description does not need to detail return values. It adequately references the prerequisite config and the remote_id source. For a simple get-config operation, the description is nearly complete, though it lacks error handling guidance.

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?

The description adds meaning to the remote_id parameter by referencing pdm_remotes_list. However, the second parameter (proximo_target) is not mentioned. With schema description coverage at 50%, the description partially compensates but does not fully document all parameters.

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: 'get configuration for one PDM-registered remote'. It distinguishes from the sibling list tool (pdm_remotes_list) by targeting a single remote, and clarifies that no secrets are returned.

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 mentions a prerequisite ('Needs PROXIMO_PDM_* config') and implies that the remote_id should come from pdm_remotes_list. However, it stops short of explicitly stating when to use this tool over alternatives or when not to use it.

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