manage_pds_cache

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

Without annotations, the description should disclose behavioral traits like destructiveness. It mentions 'refresh operations' but does not warn that actions like 'clean' or 'build_metadata' may alter or delete data. No information on permissions, side effects, or rate limits.

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 a single sentence and is concise, but it is vague and does not use the space effectively. It could be restructured to front-load more specific behaviors or parameter hints without being verbose.

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's complexity (8 parameters, multiple actions, potential destructiveness) and lack of annotations or schema descriptions, the description is insufficient. It does not explain the output schema or provide enough context for an agent to safely invoke the 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 0%, and the description adds no information about parameters. The 8 parameters (especially 'action' with 6 enum values, 'category', 'mission', etc.) are left entirely to the schema, which lacks descriptions. The description does not compensate for the schema deficiency.

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 states it manages PDS cache and metadata/catalog refresh operations, which is clear enough but uses the generic verb 'manage'. It distinguishes from siblings like 'manage_cdaweb_cache' by specifying 'PDS', but lacks specificity about the range of actions (status, clean, refresh, etc.).

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?

No guidance on when to use this tool versus alternatives such as 'manage_cdaweb_cache' or when not to use it. The description does not mention prerequisites, preferred contexts, or exclusions.

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