find_app_by_bundle_id

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

With no annotations, the description carries the behavioral disclosure burden. It usefully states that a missing app returns None, which is a key branch for an agent to handle. 'Look up' implies a read-only operation, though it does not explicitly address auth or rate limits.

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?

One tight sentence that front-loads the action and lookup key, then appends the important None-on-miss behavior. No filler or redundant restating of the tool's name.

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 one-parameter read tool with an output schema present, this is largely complete: it says what it does and what it returns on a missing app. It is only slightly incomplete in not explaining when it should be preferred over sibling lookup/list tools.

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 schema only provides a property name and type (bundle_id: string) with 0% coverage. The description adds the critical format example com.example.app, which clarifies the expected value well enough for a single simple parameter.

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 states a specific verb ('Look up'), a resource ('app'), and the lookup key ('bundle identifier'), with an example format. This distinguishes it from get_app and list_apps reasonably well, though it does not explicitly name sibling alternatives.

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 provided about when to use this tool over list_bundle_ids, get_app, or list_apps. An agent must infer that having a bundle ID is the trigger, and there are no exclusions, prerequisites, or fallback hints.

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