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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds the non-obvious part: 'opens nothing by itself', plus the exact shape of the return value (step-by-step screens, buttons, fields) and the handoff to browser tools. The AestheticsPro API paragraph explains that no self-serve API exists, which justifies the browser-automation path. It does not describe output size or failure modes, but the critical behavioral distinction is disclosed.

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 operational content is front-loaded: what it returns, that it opens nothing, and what to do next. The closing API paragraph is longer than necessary for selecting this individual tool, with vendor pricing and a check date that read as supporting evidence rather than actionable guidance. Still, every sentence serves the justification of the browser-mediated workflow.

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 zero-parameter, read-only guidance tool with no output schema, the definition covers what comes back, the side-effect profile, and the follow-up step. An agent has enough to call it correctly and know that a browser tool must be used afterwards. Slightly more on how to scope or filter the outreach calendar request would make it fully 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?

The tool takes zero parameters, so the schema carries no ambiguity and the baseline is 4. The description adds nothing further about parameters, but nothing is needed for an argument-free tool.

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 states a specific resource (the outreach calendar) and, crucially, clarifies the real behavior: it returns step-by-step instructions (screens, buttons, fields) rather than performing the view itself. The first sentence's 'View outreach calendar in the user's own AestheticsPro account' reads slightly like the tool performs the action, but the second sentence immediately corrects that. It does not explicitly distinguish this outreach calendar from sibling calendar views such as aestheticspro_view_appointment_calendar.

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?

It gives a clear usage sequence: this tool first, then execute with the cotlet_browser_* tools in the user's Cloud Browser session. The API note explains why a guidance tool rather than an API call is required, which is genuine when-to-use context. It stops short of naming when NOT to use it or which sibling calendar tool to pick for other calendar types.

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