pbs_apt_repositories_get

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

No annotations provided, but description starts with 'READ-ONLY'. Describes expected output shape, notes it is not live-verified, and explicitly states that upgrade execution is not exposed by the API. This fully informs the agent of the tool's scope and limitations.

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?

Five concise sentences that are front-loaded with the primary purpose. No redundant information; every sentence adds value.

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?

Despite no annotations, the description provides sufficient context: expected output shape, coordination with sibling tools, configuration requirement, and explicit limitations. An output schema exists, so return values are already documented.

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%, so baseline is 3. The description adds no additional meaning beyond what is already in the input schema descriptions. The note about 'Smoke-confirm' is not parameter-specific.

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 retrieves APT repository configuration of a PBS node with a specific verb and resource. Differentiates from sibling tools by mentioning coordinates needed for pbs_apt_repository_set and pbs_apt_repository_add.

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 states the tool is read-only, clarifies it does not handle upgrades, and mentions configuration requirements (PROXIMO_PBS_* config). Provides context on when to use and what it governs.

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