admob_list_apps

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

No annotations are provided, so the description carries the burden. It states 'List all apps' implying a read-only operation with no side effects, which is accurate. However, it does not disclose any potential latency, rate limits, or whether the list is paginated, which would be useful.

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 concise at two sentences, with no redundant information. It is front-loaded with the main action and follows with a requirement. One sentence could be trimmed if 'Requires AdMob authentication' were implied by context, but it's acceptable.

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 that the tool has no parameters and no output schema, the description is minimally complete. However, it could be more useful by explicitly comparing to sibling tools or mentioning the scope ('all apps') and any authentication nuance.

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 tool has no parameters, and the schema coverage is 100%. The description adds no further details about parameters beyond what the schema provides, but since there are none, it is adequate. A higher score would require clarifying that no input is needed.

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 the verb 'list' and resource 'all apps registered in your AdMob account'. However, it does not differentiate from the sibling tool 'admob_list_ad_units' which also lists entities, missing a chance to clarify that this tool lists apps specifically.

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 mentions 'Requires AdMob authentication' as a prerequisite, which is helpful. However, it provides no guidance on when to use this tool versus alternatives (e.g., using 'admob_list_ad_units' for ad units), and no conditions for when not to use it.

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