supportpages_connect_repository

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

Annotations only cover safety (readOnlyHint=false, openWorldHint=true, destructiveHint=false); the description adds rich context beyond them: the browser sign-in, consent prompt, project selection, and the explicit negative boundaries ('never approves consent, chooses a repository, uploads local articles or starts generation'). This tells the agent exactly what the tool will and will not do.

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?

Dense but front-loaded: the alias identity and core action come first, then the step sequence, then the boundaries. Every sentence carries operational information, though the resume/next-step sentences are slightly compressed and introduce the mismatched parameter 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 multi-step interactive tool with a nested resume object and an output schema, the description covers the interaction protocol, re-call semantics, and explicit non-actions well. It loses a point for the next_arguments/resume_arguments inconsistency, which leaves the resume contract ambiguous.

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 only 14% for 7 parameters, so the description must compensate and largely does not. It mentions project_id and the resume flow, but the resume parameter it references is called 'next_arguments' while the schema defines 'resume_arguments' — a naming mismatch that will confuse an agent, and action, feature, workspace, and article_id are never explained.

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 and resource ('connect a repository') and frames itself as a compatibility alias for supportpages_setup_hosted, which an agent can use to distinguish it from the canonical sibling. It is somewhat muddied by 'the original requested hosted action', but the core action is clear.

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?

Describes the interactive loop explicitly: opens sign-in first, asks which help centre, requests consent, then opens the connection/repair page, and says to call again with next_arguments after each step. It does not, however, say when an agent should prefer this alias over supportpages_setup_hosted, so the alternative-selection rule is left implicit.

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