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

With no annotations provided, the description carries the full burden. It discloses that the input can be free text or code and hints at result content, but it does not explain how results are returned, whether there are limits, how matching works, or what 'what you get' actually looks like.

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 very short and has no wasted verbiage, but it is cryptic and under-specified. It reads more like a tagline than a structured tool description for an agent.

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?

Given the absence of an output schema and annotations, the description should explain what the search returns and how to use q effectively. It does neither clearly, leaving an agent to guess at the response shape, query interpretation, and relationship to the many sibling search tools.

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 schema only defines q as a string with no description, so coverage is 0%. The description adds some meaning by saying the query accepts free text or code, which goes beyond an empty schema. However, it does not clarify format, behavior with no q, or result semantics.

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 identifies the resource ('pulsar') and suggests the content it covers ('what it is, what you get, what you pay'), which gives a vague sense of purpose. However, it never explicitly states the search behavior, and it does not distinguish this tool from siblings like pulsar_get or other *_search tools.

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?

'Free text or code' gives a minimal hint that the query can be natural language or code, but there is no guidance about when to use pulsar_search versus pulsar_get or other searches. No exclusions, alternatives, or contexts are provided.

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