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

With no annotations, the description carries the full behavioral burden. "public" weakly implies an unauthenticated read, but nothing is said about pagination, rate limits, result ordering, or what the catalogue metadata actually contains beyond the single word "metadata".

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 front-loaded sentence with no filler. Every word (public, catalogue metadata, by keyword) carries information about scope and method.

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?

No annotations, no output schema, and 0% parameter coverage across two parameters. For a search tool that returns a variable result set, the definition leaves result format, count behavior, and parameter meaning undocumented.

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 0%, so the description must compensate and largely does not. "by keyword" loosely describes the query parameter, but the limit parameter is entirely unaddressed, leaving no guidance on result count.

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 ("public Terraphim marketplace catalogue metadata") with the mechanism ("by keyword"). It implicitly separates itself from list_skills (enumerate) and show_skill (retrieve one), but never names those siblings explicitly.

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?

Usage is only implied: "by keyword" hints that this is the lookup path rather than enumeration. There is no statement of when to prefer it over list_skills or show_skill, nor any prerequisite or exclusion.

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