splithub_init

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

No annotations exist, so the description carries the full load and does well: it discloses concrete side effects (writing config/framework files, wrapping App.tsx and app/_layout.tsx in <SplitHubProvider>, adding screen tracking, writing a GitHub workflow). It does not cover auth requirements or exact permissions, leaving a minor gap.

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?

Front-loaded with the core purpose, but the body is one sprawling run-on sentence stuffed with parentheticals and pipe-delimited status values (added | already | manual: wire nextStep by hand), which hurts scannability.

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?

With no annotations, no output schema, and only 33% schema coverage, the description is behaviorally rich but leaves real gaps: what changes under mode='self', whether key is required in self mode, and what the tool returns. Adequate for a scaffolding tool but not complete.

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?

Coverage is only 33%. The description explains githubAction well ('also write a GitHub workflow (checks on PRs, results comment on a schedule)') and touches cloud mode, but never explains the 'self' enum value or when 'key' is needed beyond the schema's own 'public key pk_… when known'. Useful but incomplete compensation.

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?

States a specific verb+resource ('Set up SplitHub in this project') and then enumerates exactly what it creates: config file, framework files, agent skills, React Native wiring, native install lines. It also differentiates from siblings by directing cloud-mode users to splithub_login.

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?

Explicitly says 'Use once per project' and routes cloud-mode connection steps to splithub_login. It gives clear context for invocation but no explicit when-not-to-use it or what to do if already initialized (though 'app.entry.status added | already' implies re-run safety).

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