pdm_remote_version

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

No annotations provided, so description carries full burden. Explicitly declares 'READ-ONLY' and 'No state change', and indicates return type. Discloses proxied nature and config requirement. Lacks details on rate limits or error handling, but for a read-only tool, this is sufficient.

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 three sentences, no fluff. Starts with 'READ-ONLY:' label. Front-loaded with most important info: purpose, state, return value, then usage hint, then config requirement. Efficient and well-structured.

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 (return value documented elsewhere), the description is complete: it mentions return type, prerequisite, and config. For a simple get-version tool, no further details are needed.

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 100%, so schema already documents both parameters. Description adds only that remote_id is 'as shown in pdm_remotes_list', which ties to a sibling tool. This adds small value, but baseline is 3 due to complete schema coverage.

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 is a read-only operation to get version info for one PDM-registered remote, proxied through PDM. Distinguishes itself by specifying the single remote scope and the proxied nature, differentiating from sibling tools like pdm_remotes_list.

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?

Explicitly mentions a prerequisite (use pdm_remotes_list first) and required configuration (Needs PROXIMO_PDM_* config). Does not explicitly state when not to use, but the context is clear. Lacks explicit alternatives for similar tasks, but the guidance is strong for the intended use case.

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