getAds

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

The description does not disclose any behavioral traits beyond the basic action. No annotations are present, so the description carries the full burden. It fails to mention side effects, authentication requirements, rate limits, or any other 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?

The description is extremely concise at one sentence, which is positive, but it sacrifices necessary detail. It is front-loaded but does not earn its place fully due to missing information.

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 five parameters, no output schema, and eleven sibling tools including 'getMyAds', 'postAd', and 'updateAd', the description is far too sparse. It does not provide enough context to understand the tool's role in the P2P marketplace domain.

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?

With 0% schema description coverage, the description adds no meaning to the parameters tokenId, currencyId, side, page, or size. None of these are explained, leaving the agent to infer from naming alone, which is insufficient for reliable invocation.

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 'Get online P2P advertisements,' which clearly identifies the action and resource. However, it does not differentiate from the sibling tool 'getMyAds', which likely returns the user's own ads, creating ambiguity about whether this tool returns all public ads or something else.

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 alternatives. There is no mention of context, prerequisites, or scenarios where another tool like 'getMyAds' would be more appropriate.

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