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

There are no annotations, so the description carries the full burden. It discloses what the results are about ('what it is, what you get, what you pay') and input style ('Free text or code'), but it does not describe output format, scope, limitations, or whether this is strictly a read/search 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 description is concise and easy to scan, using one short sentence plus a brief input hint. It avoids filler and clearly front-loads the core value proposition, though the phrasing is more promotional than operational.

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 one-parameter search tool with no output schema and no annotations, the description gives some context about content areas but omits essential selection cues. It does not explain what a typical result looks like, how to distinguish it from sibling tools, or what 'code' input entails, leaving an agent under-informed.

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 provides only a string parameter 'q' with no description, and schema description coverage is 0%. The description adds some meaning by saying 'Free text or code,' which tells the agent that q accepts natural language or code snippets, but it stops short of providing examples, constraints, or expected format.

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 conveys the topic ('How pulsar compares — what it is, what you get, what you pay') and indicates input flexibility ('Free text or code'), but it lacks a clear verb and resource. It does not explicitly state that this tool searches or returns comparison information, and the 'pulsar' focus could be confused with sibling tools like pulsar_search.

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 guidance is given about when to use measure_search versus alternatives such as measure_get or pulsar_search. The only implied context is 'pulsar compares,' which is too indirect to help an agent choose among the many sibling search tools.

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