Search Tools

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds value on top: 'makes no Canvas calls and works before a token is set' is a non-obvious auth-independence property, and it discloses the return format (names + one-line descriptions). That is exactly the extra context annotations cannot express.

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?

Three short sentences, front-loaded with the action then the return value then the calling context. Every sentence carries distinct information with no repetition of the title or name.

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 zero-required-parameter discovery tool with full schema coverage and no output schema, the description supplies purpose, return form, and auth prerequisites — everything an agent needs to call it correctly and to know when it will work.

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 100%, with the group list enumerated and query documented including 'Omit to list everything.' The description adds no parameter detail beyond the schema baseline, so a 3 is appropriate.

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?

States a specific verb and resource ('search this server's tools by keyword') plus the return shape ('matching names with one-line descriptions'). The phrase 'this server's tools' distinguishes it from course-content search siblings like smart_search and search_course_content without needing to name them.

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?

Gives a clear use case — 'find the right tool among the 200+ available' — and adds a timing condition ('works before a token is set') that tells the agent it is safe to call prior to auth. It does not explicitly exclude or route to near-neighbors like smart_search or search_course_content, which is the remaining gap.

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