APIbase

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

With no annotations provided, the description carries the full burden. It correctly implies a read-only operation via 'Get' and discloses the return payload structure ('HTML content and metadata'). However, it lacks disclosure of error behaviors (e.g., missing page handling), caching, or rate limiting.

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, front-loaded sentence of 12 words with zero redundancy. Every phrase contributes essential information about the operation, resource, identifier, and system context.

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 retrieval tool with 2 parameters and no output schema, the description adequately compensates by specifying the return format ('HTML content and metadata'). It misses explicit error state documentation but is otherwise complete for its complexity level.

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?

Input schema has 100% description coverage, establishing a baseline of 3. The description reinforces the 'slug' parameter's role but does not add syntax details, format constraints, or semantic relationships between parameters beyond what the schema already provides.

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 provides a specific verb ('Get'), clear resource ('full HTML content and metadata'), and scope ('specific generated page by slug'). The '(AIPush)' tag and 'generated page' qualifier effectively distinguish it from sibling tools like aipush.pages.list (listing) and aipush.pages.generate (creation).

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?

The description explicitly references prerequisite tools by stating the slug is 'Returned by aipush.list_pages or aipush.generate_page', providing clear workflow context for when to invoke this tool. While it doesn't explicitly state negative cases (when not to use), the implicit guidance is strong.

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