pplx_gpt55

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

No annotations provided, so description bears full burden. Only discloses cost and subscription; lacks information on behavior (e.g., what happens on success/failure, data handling, rate limits). Minimal transparency.

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?

Two sentences, no fluff, front-loaded with model name. Highly concise.

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 tool has 2 params and output schema exists, description still misses core purpose and parameter context. Agent cannot infer what the tool actually does (e.g., generate text) or how to use parameters.

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 has 2 parameters with 0% description coverage, and the description adds no information about parameters. Does not explain 'query' or 'source_focus' meaning, default, or usage.

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 tool as GPT-5.5 model and mentions cost and subscription, but does not explicitly state the verb (e.g., 'generate', 'query') or differentiate from siblings like pplx_gpt54. Purpose is implied but not clear.

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?

Provides cost and subscription requirement, which gives some context, but no guidance on when to use this versus alternative models (e.g., pplx_claude_opus). No mention of when not to use or prerequisites beyond subscription.

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