pdm_resources_status

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

No annotations provided, but description explicitly declares 'READ-ONLY' and 'No state change', which fully discloses the read-only, non-destructive behavior. Also mentions return format 'dict of counters'.

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?

Two concise sentences plus a brief config note. Front-loaded with 'READ-ONLY' and key purpose. No fluff, 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?

Output schema exists (not provided but noted), so the description's mention of 'dict of counters' suffices. Parameter is well-covered, sibling differentiation provided, and config requirement stated. Complete for a read-only status tool.

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% for the single optional parameter proximo_target, and the description adds no additional semantics beyond what the schema already documents. Baseline of 3 is appropriate.

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 the tool returns 'aggregated fleet status counters' across all PDM remotes, uses specific verb 'status', and distinguishes from sibling tool pdm_resources_list for per-resource 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 says 'No state change' and directs to pdm_resources_list for per-resource details. Also notes configuration requirement (PROXIMO_PDM_* config), providing clear when-to-use and when-not-to-use guidance.

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