social_media_posting_start_google_oauth

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

Annotations already include readOnlyHint=true, idempotentHint=true, and openWorldHint=true, which cover the safety and idempotency profile. The description adds no extra behavioral context beyond stating the action. It does not explain what 'starting OAuth' entails (e.g., returning a redirect URL, initiating a consent flow), so beyond the annotations, there is minimal disclosure.

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, concise sentence that immediately states the action. No filler, no repetition, and it is appropriately sized for such a simple tool.

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 an OAuth starter tool with no output schema and annotations covering safety, the description provides the basic purpose. However, it does not explain critical nuances like what the result of 'starting' is, what 'reconnect' means, or when to pass a 'locationId'. While the schema documents parameters, the descriptions of parameters are vague (e.g., 'Page', 'Reconnect'), so the tool is not fully self-explanatory.

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?

The input schema has 100% description coverage for all four parameters, so the schema already documents each parameter. The description does not add any semantic detail or clarify parameter usage (e.g., what 'reconnect' or 'page' mean in context). Baseline of 3 is appropriate because the schema carries the burden.

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 verb 'Starts' and the resource 'OAuth For Google Account', which is specific and distinguishes this tool from sibling OAuth tools for Facebook, Instagram, LinkedIn, etc. It is not a tautology and conveys exactly what the 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?

The description provides no guidance on when to use this tool versus the other social_media_posting_start_*_oauth siblings. It does not mention prerequisites, conditions, or alternatives, leaving the agent to infer usage from the tool name alone.

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