ch_dp_search_guidelines

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

Without annotations, the description should disclose behavioral traits like read-only nature, authentication, or rate limits. It only says 'Search' (implied read-only) but does not explicitly confirm safety or mention any limitations, leaving significant gaps for a search tool.

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, focused sentence that conveys key information without fluff. It could benefit from slight restructuring (e.g., listing), but it is appropriately concise for the tool's simplicity.

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?

With 4 parameters, no output schema, and no annotations, the description lacks information about return format, pagination (limit parameter mentioned but not explained), error handling, or any constraints. It only provides examples, leaving the agent underinformed for reliable invocation.

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% with all parameters described. The description adds valuable examples for the query parameter (e.g., 'Cloud Computing', 'neues DSG') and implies topics, going beyond the schema's generic descriptions. This helps agents form effective queries.

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 verb 'Search' and the resource 'FDPIC guidance documents', and lists specific document types (Leitfäden, Erläuterungen) and topics (cloud computing, new DSG). This distinguishes it from sibling tools like ch_dp_search_decisions (decisions) and ch_dp_get_guideline (single document).

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?

The description provides no guidance on when to use this tool versus alternatives like ch_dp_search_decisions or ch_dp_list_topics. It does not mention prerequisites or context that would help an agent choose correctly.

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