search_modules_messages

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

Annotations are absent, so description should cover behavioral traits. It only mentions the 'detailed' flag and notes the tool is 'undocumented'. No disclosure of auth needs, rate limits, or read-only nature.

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?

Very concise (two sentences), but one sentence is essentially a note about being undocumented, which could be better placed. Could include more context without losing conciseness.

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?

Missing differentiation from sibling 'search_messages' and no explanation of 'modules' in the tool name. Output schema exists but not described. Overall incomplete for a search tool with multiple siblings.

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%, and the description adds no significant value beyond what the schema already provides. The 'detailed' hint is redundant with schema description.

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 action (search) and resource (messages), but it does not differentiate from the sibling tool 'search_messages'. The term 'undocumented' is odd but doesn't obscure purpose.

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. alternatives like 'search_messages' or 'search_all'. The only hint is about the 'detailed' parameter, but no context on when to prefer this tool.

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