List AdMob apps

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is known. The description adds value by specifying the fields returned and describing pagination behavior ('Set all=true to page through every app (capped for output size)'). No contradictions.

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 well-structured sentences with front-loaded action. Every sentence adds value: first states purpose and included fields, second gives usage guidance on pagination. No wasted words.

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 list tool with 4 parameters and no output schema, the description is fairly complete. It covers the basic functionality, fields returned, and pagination behavior. It could mention default behavior when all=false or other edge cases, but overall it provides sufficient context.

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 coverage is 50% (two params have descriptions). The description explains the 'all' parameter's effect, which adds meaning beyond the schema's 'Follow pagination and return all apps (capped)'. However, it does not address 'pageSize' or 'pageToken', which are common but not described. The 'publisherId' parameter has a schema description but is not mentioned in the tool description.

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 clearly states it lists apps under an AdMob account and specifies the fields included (app id, platform, approval state). The verb 'list' and resource 'apps' are specific. It doesn't explicitly distinguish from sibling list tools, but the name and resource difference make it 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?

The description provides guidance on using 'all=true' for pagination with a cap, but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage context is implied by the tool's resource focus.

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