Set the big page title

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine context by saying "Replace" (the existing header title is overwritten) and by disclosing the current default 'Título de la página', but says nothing about required auth/session state or what happens when the title exceeds the 120-character cap.

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?

A single sentence that front-loads the action and then qualifies the target element; every clause earns its place and there is no filler.

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 setter with annotations and no output schema, the description covers the essential facts: what changes, that it is a replacement, and the current default. Only operational preconditions (an open, loaded page) are left unstated.

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%, so the description carries the burden for the single 'title' parameter. It does useful disambiguation by pinning the value to the large page-header title (as opposed to a page name or URL slug), but it adds nothing about the minLength 1 / maxLength 120 constraints or accepted formatting.

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?

"Replace the large title shown in the page header" gives a specific verb (replace) and a specific resource (the big page-header title), and the parenthetical default value anchors exactly which element is meant. That implicitly separates it from block-insertion siblings like gsites_add_text or gsites_type, though no sibling is named explicitly.

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 only implied: an agent can infer this is the tool for changing an existing page's header title rather than adding content. There is no statement of prerequisites (site/page must be open), no exclusions, and no pointer to alternatives such as gsites_add_text for body text.

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