growsurf_mobile_sdk_guide

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds the topics covered but does not disclose any additional behavioral traits, such as required setup or output format. It provides some context but not deep behavioral detail.

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 a single, front-loaded sentence with no wasted words. It efficiently states the purpose and key features, though it could structure the content with more detail without becoming verbose.

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 tool with 7 parameters and an output schema, the description is too sparse. It does not explain what the generated output looks like, which parameters are essential, or any constraints. Even with annotations and an output schema, an agent would struggle to call this correctly without additional information.

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 description coverage is 0% and the description does not explain any of the 7 parameters (e.g., platform, campaignId, mobilePublicKey, participantState). An agent receives no guidance on how to set these parameters or what each represents, leaving the schema enums and defaults as the only clues.

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 generates guidance for the native iOS/Android SDK version 0.4.0, listing specific features like attribution, shareUrl sharing, trackShare, and the native GrowSurf Window. This distinguishes it from siblings like growsurf_integration_guide and growsurf_client_snippets.

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?

The description does not mention when to use this tool versus alternatives. With many sibling guide/snippet tools present, there is no explicit differentiation in terms of usage context, such as 'for web use X' or 'for client-side snippets use Y'.

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