pbs_datastore_get

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

No annotations provided, so description carries full burden. It labels the tool as 'read', indicating non-destructive behavior. Mentions returned data but lacks detail on error handling or permission requirements. Adequate but not comprehensive.

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?

Three concise sentences: main purpose, alternative tool, prerequisite. Front-loaded with essential information, no wasted words.

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 tool has an output schema, the description only needs to summarize return content, which it does (path, gc-schedule, etc.). Includes necessary context for usage.

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?

Description adds meaning to the 'name' parameter by stating it's a datastore name. The 'proximo_target' parameter already has a detailed schema description. With 50% schema coverage, the description partially compensates for the missing name description.

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?

Description clearly states 'Get full config of one PBS datastore by name (read)', specifying the verb, resource, and scope. It distinguishes from siblings by mentioning that pbs_datastore_status is for runtime usage stats.

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 explicit guidance to use pbs_datastore_status instead for runtime stats. Also mentions the prerequisite 'Needs PROXIMO_PBS_* config'. Could be slightly more explicit about when not to use, but adequate.

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