get_collection_rules

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

Describes the return format as a list of dictionaries with rule and metadata, and explains default behavior for top_n and rule_types. No annotations exist, so the description adequately covers behavior for a retrieval 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?

Well-structured with purpose, note, example, args, and returns. Slightly lengthy but each section is useful and not redundant.

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?

Covers essential aspects including parameter details and return format. Could mention api_key usage and error handling, but overall sufficient for the tool's complexity.

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?

Adds meaning for three of four parameters beyond schema (e.g., rule_types values, top_n default, collection_id description). Missing api_key documentation, but schema coverage was 0%, so description adds significant value.

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?

Clearly states 'Retrieve top N community rules and all curated hunting rules for a specific collection', specifying a verb and resource, and differentiates from sibling tools that handle other entities or operations.

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 examples and details on how to use the rule_types parameter, but does not explicitly mention when not to use this tool or contrast with alternatives like get_hunting_ruleset.

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