search_modules_files

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

No annotations are provided, so description must carry behavioral info. It only labels the endpoint as 'undocumented,' implying instability, but lacks disclosure of side effects, rate limits, or output behavior. Output schema exists but description adds no context.

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?

Extremely brief but not appropriately concise—missing essential information. Single sentence fails to provide value, making it under-specified rather than concise.

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 search tool with 3 parameters, an output schema, and siblings, the description is critically incomplete. It does not explain scope, pagination, usage context, or return value structure, leaving the agent without adequate guidance.

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 0% with no parameter descriptions. The description does not explain any parameter beyond the schema property names (query, cursor, count). Agent must guess semantics from names alone.

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 states 'Search files' but includes 'undocumented session endpoint' which is confusing and doesn't clarify what 'modules' means. There is a sibling tool 'search_files' that likely overlaps, but no differentiation is provided.

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 versus other search tools like search_files or search_modules_channels. Agent has no context to decide which search tool to invoke.

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