find_resources

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only search operation ('Search', 'Returns') and explains the return tagging (`added: true`). While it does not explicitly state that it makes no modifications, the semantics strongly imply a non-mutating operation.

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 core description is one sharp sentence covering purpose and return behavior, with a second sentence providing current state context. While concise, the second sentence is a state snapshot that may become stale and is not a tool behavior, slightly reducing focus.

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 simple search tool with one parameter and no output schema, the description adequately covers the search scope, query semantics, and result tagging. It lacks explicit result field details or usage edge cases, but the essential behavior is well described.

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?

The input schema only provides a property `query` with no description. The description explains the query as a free-text search against name/description, giving concrete meaning to the parameter and fully compensating for the 0% schema description coverage.

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 uses the specific verb 'Search', identifies the resource as the AAuth registry's discoverable resources, and specifies the free-text query mechanism against name/description. This clearly distinguishes it from sibling tools like list_resources and add_resource.

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 the tool is for searching the registry but does not explicitly state when to use it over list_resources or add_resource, nor does it provide alternative guidance. It is a clear purpose statement but lacks explicit when-to-use or when-not-to-use criteria.

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