Connect developer console

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

Beyond the annotations, the description discloses critical behavior: the bridge reads secrets locally, the app stores them in the OS keychain, and credentials are never returned. It also states file-location and extension restrictions, which an agent must know before calling the tool.

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 front-loaded with the core action and has no wasted sentences. The long parenthetical about allowed file paths and extensions is dense but earns its place as operational constraint.

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 credential-connection tool with no output schema, the description covers what is stored, where it is stored, that credentials are not returned, and how to pass secrets safely. It stops short of explaining whether the connection is validated immediately or whether test_console should follow, but it is otherwise sufficient for correct invocation.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: agents should pass file paths rather than inline secrets, and those files must be .p8/.pem/.json/.txt in the owner's Downloads, Desktop, or Documents folder. It also groups parameters by store (apple vs. google), which helps selection.

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 names a specific verb and resource: connecting an App Store Connect API key or Google Play service account. It distinguishes the two auth paths and states the effect (credentials stored in the OS keychain), so an agent can tell exactly what this tool does.

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?

It says the tool is needed for console apps, publishing, and own-app metadata, which gives clear context for when to call it. It does not name alternatives such as test_console or disconnect_console, nor does it state when not to use this tool, so it falls short of the explicit when/when-not pattern.

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