search_subscriptions

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

With no annotations provided, the description must disclose behavior. It includes the endpoint (POST /subscription/search) and a tier hint (readonly-owner), which adds some context. However, it does not explain pagination, response format, authentication requirements, or any side effects, leaving significant gaps.

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 a single concise sentence with useful metadata (endpoint, tier). It is front-loaded with the purpose and contains no fluff, though its brevity does not fully serve the tool's complexity.

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 tool has 11 parameters, 0 required, no output schema, and 36 sibling tools, the description is too sparse. It does not explain filter behavior, return shape, or how it fits into the broader toolset, making it incomplete for effective selection and invocation.

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 only 9% (only 'active' has a description). The description adds no parameter details whatsoever, failing to compensate for the 11 undocumented parameters, including nested objects like extra_filters.

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 clearly states the verb 'Search' and resource 'subscriptions (recurring service plans)' and specifies that it returns matching IDs. This differentiates it from get_subscriptions, which likely returns full subscription objects, though it does not explicitly name the sibling.

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 provided on when to use this tool versus get_subscriptions or other search tools. The description only states what it does; there is no mention of 'use this when you need IDs' or alternatives to consider.

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