search_rule

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

No annotations provided. The description indicates both title and full text search, but the 'full_text' parameter defaults to false, creating ambiguity about default behavior. No mention of pagination, result structure, or required permissions.

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?

One sentence with an example; no wasted words. However, it could be more structured (e.g., bullet points) for clarity.

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 5 parameters, no output schema, and sibling tools, the description is too brief. Lacks details on output format, campus usage, pagination, and when to use 'full_text'. Incomplete for effective selection.

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 60% (3 of 5 parameters described). The description adds minimal parameter context: 'keyword search (title/full text)' implies keyword and full_text relevance but does not explain 'limit', 'offset', or 'campus'. Examples help but don't compensate for undocumented params.

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 searches Dongguk University regulations by keyword in title or full text, with examples. This is specific and distinct from sibling tools like 'get_rule_content', but does not explicitly differentiate from 'search_rule_deep'.

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 vs. siblings, no prerequisites or exclusions. The description only implies a keyword search use case.

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