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

No annotations are provided, so the description carries the full disclosure burden, and it adds nothing beyond the name: no indication of whether this reads or mutates state, what it returns, whether results are paginated or ranked, or what "listed" entails permission-wise. A three-word description for a no-annotation tool leaves the agent guessing entirely.

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?

It is a single three-word phrase with no wasted clauses and nothing to front-load. However, this is brevity by omission rather than by discipline — the sentence is short because it conveys almost no information, not because it is tightly edited.

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?

With zero annotations, no output schema, and no parameters, the description is the only channel available to explain behavior — and it delivers nothing about result contents, scope, or limits. An agent cannot form a correct call or interpret a response from this definition.

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 declares zero parameters, so there is no parameter semantics for the description to explain; the baseline for 0 params applies. The one notable gap — that a search tool accepts no query argument at all — is left entirely unexplained, but that is a schema design issue rather than a description deficiency.

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?

"Search listed parts" names a verb (search) and an object (listed parts), but "listed" is unresolved — listed where, by whom, in what registry — so the agent cannot tell what corpus is being queried. There is no differentiation from the sibling tool "list", which an agent could easily mistake for this one.

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 gives no when-to-use, when-not-to-use, or alternative. With siblings like "list", "harvest", and "transplant" in the same family, the agent has zero signal for choosing this tool over them.

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