99 ride categories

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

The annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the additional burden is low. The description adds genuine behavioral context beyond annotations: the returned categories are driven by pGetConfig, include extra products from that config, and exclude 99Food/99Pay. This is useful scoping information with no contradiction to annotations.

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 only two short sentences and contains no padding or redundant restatement of the title. The inclusion/exclusion structure is efficient and scannable. It loses a point because the first sentence is grammatically awkward and relies on unclear jargon ('Shipped', 'pGetConfig'), reducing readability.

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 read-only listing tool with no required parameters and self-describing enum schemas, the description is minimally adequate: it identifies the category scope and the config-dependent source. However, with no output schema present, it should have said more about what the returned list contains or how privacy_mode and response_format alter the response, so an agent is left to infer some behavior.

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 needed to explain or contextualize privacy_mode and response_format, but it mentions neither. The schema's enums and default provide some structure, but the description adds zero semantic value about how these parameters affect the returned category list.

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 title and description make clear that this tool exposes ride categories for 99Pop and 99Moto, plus any extra products returned from pGetConfig. It explicitly scopes itself by saying 'Not 99Food/99Pay', which helps distinguish it from broader product-family tools. It loses the top mark because there is no clean action verb like 'returns' or 'lists', and the phrasing 'Shipped ... product list' is cryptic.

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 implies this tool should be used for ride categories and explicitly says it is not for 99Food/99Pay, which is useful exclusion guidance. However, it does not state when to choose this over sibling tools such as ninenine_capabilities or how to route food/pay requests to an alternative.

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