search_modules_dms

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

No annotations are provided, so the description must fully inform. It mentions 'undocumented session endpoint' but does not disclose other behavioral traits like required authentication, error handling, or read-only status. Minimal transparency.

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 very concise (one sentence) and front-loaded. Every word earns its place. Could be slightly more structured with additional context, but remains efficient.

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?

Given the existence of many sibling search tools, the description does not provide enough context to guide selection (e.g., why use this over search_messages?). It also omits details about pagination, rate limits, or session requirements. Output schema exists but is not referenced.

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%, so baseline is 3. The description adds no parameter-specific information beyond the schema's own descriptions (e.g., query matched against DM content). No added 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?

Description clearly states 'Search within direct messages only', specifying a specific verb (search) and resource (direct messages). It distinguishes from sibling tools like search_messages and search_all by scoping to DMs.

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 implies when to use (searching DMs), but does not explicitly mention when not to use or name alternatives. However, the sibling names provide context, and the phrase 'undocumented session endpoint' hints at experimental use.

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