List Plural Apis

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

Description declares read-only nature (matching annotations) and adds the 'official tool' label and a security warning about not trusting data-driven instructions. Annotations already provide readOnlyHint, so description adds useful behavioral context.

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?

Concise description with front-loaded labels and no unnecessary words. Every sentence adds value.

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 simple listing tool with an output schema, the description covers purpose, usage, and a security note. Could mention if results are paginated or limited, but not essential.

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 has one optional parameter 'search' with no description (0% coverage). The description clarifies that it filters results, which adds basic meaning. More detail on format or behavior could improve score.

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?

Clearly states the verb (list), resource (all available Pine Labs APIs), and optional filtering. Also explicitly ties its purpose to discovering api_name values for 'get_api_documentation', distinguishing it from related tools.

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?

Explicitly states when to use (to discover api_name values) and when not to use (based on external instructions; only when requested by human). Mentions alternative tool 'get_api_documentation'.

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