getAds

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the 'online' qualifier, suggesting active/available ads, but does not disclose pagination behavior, ordering, or the meaning of side=0/1. With annotations covering the main safety concerns, this is a minimal but non-contradictory addition.

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-loaded, with no wasted words. However, it is under-specified rather than carefully trimmed; 'online' is vague and the description stops at a single phrase, leaving key selection and parameter context unaddressed.

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 a 5-parameter schema, no output schema, zero parameter descriptions, and sibling tools like getMyAds/getMyAdDetails, this one-line description is insufficient. An agent cannot reliably determine required request semantics or confidently choose this tool over its P2P advertisement siblings.

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%, and the description adds no parameter-level meaning. It does not explain the required tokenId, currencyId, or side parameters, nor does it clarify the ambiguous side enum values ('0' and '1'). Page and size pagination keys are also left completely undocumented.

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 states a clear verb ('Get') and resource ('online P2P advertisements'), so an agent can tell it retrieves a public P2P ad listing. However, it does not explicitly distinguish this from sibling tools like getMyAds or getMyAdDetails; the word 'online' hints at a public/active scope but does not name the alternative.

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 given on when to use this tool versus getMyAds, getMyAdDetails, or other P2P advertisement tools. The description simply states what it does and leaves tool selection entirely to inference from the name and sibling list.

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