proximo_find

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

Annotations already declare readOnlyHint=true, and the description reinforces READ-ONLY while adding useful behavior: how query words are matched, that a verb selects the method, the default result count, and that results include access and blast-radius tier. It does not cover permissions, rate limits, or pagination beyond the default.

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 compact and front-loaded with READ-ONLY and the core search purpose. Every sentence contributes useful information without repetition.

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?

An output schema exists, so return-value detail is less necessary, and the description does summarize the result as access plus blast-radius tier. However, for a 3-parameter tool it omits the plane parameter entirely and gives no sibling-tool routing guidance, leaving clear gaps.

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%, so the description must compensate. It explains the query parameter's matching behavior and mentions the default of 5, but it never mentions the plane parameter or its pve/pbs/pmg/pdm enum options, leaving a required routing choice undocumented.

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 gives a specific verb and resource: search every API address the planes publish. The plain-word examples clarify what is being searched, but sibling tools such as proximo_read and proximo_call are not named, so the boundary is implied rather than explicit.

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?

It implies use for discovery by saying to search API addresses in plain words and giving example queries. However, it does not state when to use this versus proximo_read, proximo_call, or proximo_plan, nor does it give any when-not guidance.

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