stellar_plugin_search

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

No annotations exist, so the description carries the full burden. It hints that results are sourced from GitHub but says nothing about authentication, rate limits, whether anything is installed or modified, or the result format — all material for a tool an agent may invoke blindly.

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?

A single short sentence with no filler and the key concept (plugin search) front-loaded. It is under-specified rather than verbose, but as written 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 takes no inputs and has no output schema, so the description only needs to convey what invocation does. It covers that minimally, but leaves the agent unsure about network requirements, whether the search is remote, and what kind of results come back.

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 defines zero parameters, so there is no parameter semantics to document and no gap for the description to compensate for. Baseline 4 applies for a parameterless tool.

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?

States a specific verb (Search) and resource (CLI plugins), and distinguishes itself from the sibling stellar_plugin_list by adding where results come from (GitHub). It is clear, but the mechanism ('using GitHub') is loose and could mean the API, raw repos, or a curated index.

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 when-to-use guidance, no mention of when to prefer this over stellar_plugin_list or other plugin tools, and no prerequisites (network access, GitHub token). The only implicit signal is that it is a search rather than a listing.

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