get_installed_app

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

With no annotations, the description carries the full behavioral burden. It discloses that this is a read-only 'Lists' operation and includes the GET endpoint, which is useful. However, it does not mention authentication, scoping edge cases, pagination, or what an 'installation' entails.

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 one focused sentence that front-loads the purpose and appends the endpoint for disambiguation. There is no filler or repetition.

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's simplicity, the description conveys the core operation and return concept (installation(s) and ID(s)). However, with no annotations, no output schema, and incomplete parameter semantics, an agent still lacks some context about response shape and edge behavior.

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 only 50%, and the required publishedInboxAppId has no schema description. The tool description only marginally compensates by referencing 'your Published Inbox App' and showing the endpoint placeholder; it does not clearly define the parameter's meaning or the extraQuery behavior beyond what the schema already says.

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 names the operation ('Lists') and the specific resource ('Inbox App installation(s) and ID(s)') scoped to the current FUB account's Published Inbox App. It is understandable on its own, though it does not explicitly distinguish itself from related inbox-app siblings like post_inbox_apps_install.

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 given about when to use this tool versus alternatives, nor when not to use it. The phrase 'for your Published Inbox App' hints at context, but there are no exclusions, prerequisites, or sibling comparisons to help an agent choose confidently.

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