nexus_search

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

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It does not state whether the search is read-only, whether it requires authentication, what side effects may occur, or how versioning affects results. The word 'versionados' adds some context but not enough for a tool with zero annotation coverage.

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 a single, front-loaded sentence with no filler. It conveys the verb, scope, and target content types efficiently, and every word earns its place.

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?

The tool is low-complexity and the schema covers both parameters well, but there is no output schema and no behavioral or usage-guidance detail. The 'limit' parameter description implies snippets are returned, which partially compensates, but the description alone leaves gaps around return format, safety, and tool selection context.

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%, and both parameters come with meaningful descriptions ('query' and 'limit'). The tool description itself does not add much beyond mapping 'termo' to the query parameter, so the baseline of 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?

The description clearly states the verb 'Busca' (search), the resource ('termo'), and the scope ('ideias, projetos, decisões e propostas versionados no Nexus'). It is clear and specific, but it does not explicitly contrast with sibling tools like nexus_get_project or nexus_list_recent, so it slightly misses the top tier for sibling differentiation.

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 is purely declarative and gives no guidance on when to choose this tool over alternatives such as nexus_get_project or nexus_list_recent. It neither mentions exclusions nor prerequisites, leaving usage decisions entirely to inference.

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