ios_manifest_analyzer

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

With no annotations, the description must carry the behavioral load; it does add that the tool "highlights insecure configurations," which tells the agent to expect analytical output, not raw JSON. It says nothing about failure modes (missing/corrupt IPA), whether analysis is static-only, or the shape of results.

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, zero filler, with the core action front-loaded and the extracted data listed second. Every clause earns its place.

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 no output schema, listing the extracted fields effectively communicates what comes back. Minor gap: no mention of error behavior or of how the "insecure configurations" findings are reported.

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 single parameter has 100% schema description coverage ("Absolute path to the IPA file to analyze"), so the schema already does the work. The description adds no syntax, constraints, or path-handling detail beyond it — baseline 3 applies.

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?

Specific verb+resource: "Parses Info.plist from an IPA file" and enumerates the exact fields extracted (bundle ID, version, URL schemes, ATS settings, background modes). This clearly separates it from the APK-side siblings, though it never names which sibling to prefer among the many ios_* tools.

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?

Usage is strongly implied — you call it when you have an IPA and want manifest-level facts — but there is no explicit when/when-not guidance and no routing against close alternatives like ios_permissions_checker, ios_entitlements_checker, or ios_google_services.

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