get_pipc_curated_corpus

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

No annotations provided. Description discloses that the list is a direct copy from PIPC portal (not curated by us) and that source URL is automatically attached for verification. This covers behavioral aspects like origin and verifiability. Could be improved by noting read-only nature more explicitly.

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 detailed but each sentence adds value. It front-loads the main purpose and then adds nuances. Could be slightly shortened by merging some lines, but overall effective structure.

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?

For a simple list retrieval tool with one parameter and no output schema, the description is comprehensive. It covers what the tool returns, its origin, its relationship to other tools, and usage sequence. No critical gaps remain.

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?

The sole parameter 'category' is fully described in the schema with enum values and defaults. The description adds context by mapping enum values to actual counts (12 laws, 23 rules) and explaining what 'all' includes. This supplements schema meaningfully.

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 clearly states the tool returns PIPC's official curated list of 12 laws and 23 administrative rules, distinguishes it from sectoral guides, and positions it as the entry point for PIPA domain. It also mentions the source URL attachment and relationship with sibling tools.

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 advises use as first entry into PIPA domain, contrasts with sectoral guides, and suggests subsequent tools (search_law, search_admin_rule, get_sectoral_related_laws) for deeper exploration. Provides 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.