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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context beyond that: it clarifies it returns only pending requests and that each item contains the lead and the property, plus the authentication requirement (Cotlet API key with app access). No pagination notes, but the added value is genuine.

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 definition of Safe Mode requests ('prospects who scheduled a viewing that waits for your approval') is stated twice almost verbatim, and the title is embedded in the body. The core routing information is present but the redundancy costs it structure points.

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 listing tool with no output schema, the description supplies what the agent needs: what is listed (pending requests), the shape of each item (lead and property), follow-up tool routing, and the auth requirement. It is largely self-sufficient given the absence of an output schema.

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 baseline is 4 and the description carries no parameter burden. It does usefully explain the identifiers present in each returned item (request_id, lead_id), which helps the agent chain calls even though those are outputs rather than inputs.

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 (Lists) and resource (pending Safe Mode requests) and defines the concept as prospects who scheduled a viewing awaiting approval. It names related siblings (grant_safe_mode_access, dismiss_safe_mode_request, get_lead), making routing clear. The content is somewhat duplicated, which slightly weakens an otherwise clear purpose statement.

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 tells the agent what to do with the results: pass request_id to grant_safe_mode_access or dismiss_safe_mode_request, and lead_id to get_lead. This is strong next-step routing. It does not state when NOT to use it or contrast with an alternative listing tool, but there is no obvious sibling alternative for this resource.

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