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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real content beyond that: 'opens nothing by itself' confirms no side effect despite the action-shaped name, and the note that Yardi has no self-serve Breeze API explains why the browser fallback exists. It still doesn't describe the shape or volume of the returned instructions.

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?

It is three sentences, front-loaded with the core behavior and followed by the next-step routing. Some phrasing does not earn its place, notably 'from ChatGPT, Claude or any AI agent' and the date-stamped parenthetical '(checked 27 Oct 2026)', but the total length stays reasonable.

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, no-output-schema tool the description covers what it returns (step-by-step Yardi guidance) and what the agent should do next. Nothing needed to call it correctly is missing. A brief note on what happens if the tenant or message is unavailable would have made it 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 there is nothing for the description to disambiguate and the baseline for a no-param tool applies. The description correctly implies all inputs (tenant, message) are supplied later to the browser tools rather than here, which is useful framing.

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 names a specific verb and resource (email tenant in Yardi) and immediately clarifies the actual behavior: it returns step-by-step Yardi instructions rather than sending anything. It points to the cotlet_browser_* siblings as the execution path, which separates it from the browser tools and from yardi_text_tenant. It stops short of an explicit contrast with the sibling tenant-messaging tool.

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: call this to get the Yardi screens/buttons/fields, then perform the action with cotlet_browser_* in the user's Cloud Browser. That is actionable when-to-use guidance. It does not state when to prefer yardi_text_tenant instead, or any exclusions, so it falls short of the top tier.

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