listInboxAppInstallations

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

Discloses the prerequisite authentication via system keys and the error condition, adding value beyond the empty schema and lack of annotations. No mention of rate limits or pagination, but acceptable for a simple list operation.

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 sentences, front-loaded with the action, no wasted words, and efficiently conveys purpose and key requirements.

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?

Covers purpose, prerequisites, and a common error. Missing any mention of pagination or result format, but given no parameters and no output schema, it is reasonably complete.

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 zero parameters; description correctly adds no unnecessary information. Schema coverage is trivially 100%, and the baseline for zero params is 4, but the conciseness earns a 5.

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 tool lists inbox app installations, using a specific verb and resource. However, it does not explicitly differentiate from sibling list tools, though the resource is unique.

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?

Provides clear context by mentioning the required registered third-party system and the common 404 error for unregistered accounts, but does not specify when to avoid using this tool or recommend alternatives.

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