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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It weakly implies an informational/pricing result and that the input can be text or code, but it does not state whether the tool returns a list, performs lookups, requires authentication, or has any side effects.

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 short and front-loads the product name with no filler, which is good. However, it reads more like a tagline than a tool specification, and the brevity sacrifices the operational clarity an agent needs.

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 no annotations, no output schema, and zero schema description coverage, the description is the only context and it is incomplete. It never explains the query scope, return shape, or relationship to rider_get, leaving an agent to guess whether to pass a plan name, a code snippet, or a natural-language question.

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 exposes a string parameter named 'q' with no description, and schema coverage is 0%. The description adds some meaning by saying the query can be 'free text or code,' but it leaves unclear how the text is matched or what the query should target.

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 a resource ('Agent-Rider') and hints at content ('what it is, what you get, what you pay'), but it never states a clear verb or operation. 'Free text or code' suggests a search/query tool, yet the description does not explicitly say what the tool does or how it differs from rider_get.

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?

There is no guidance about when to use rider_search instead of rider_get or other sibling tools. 'Free text or code' is a clue about the query format, not a use-case condition, so the agent receives no selection guidance.

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