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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and a closed-world scope. The description adds useful behavior beyond annotations: a cap of 50, the fact that results are reported exactly as-is, and the important distinction that a failed load is not the same as an empty inbox.

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 front-loaded and compact: the core read operation comes first, followed by failure semantics. 'Free; changes nothing' is somewhat redundant with the readOnly annotation, but it still concisely communicates cost and safety.

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 tool with strong annotations, the description covers the essential context: scope, result cap, cost, and failed-load semantics. It does not explain the enquiry fields returned, but with no output schema this is a minor gap rather than a blocking one.

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 has zero parameters, so there is no parameter schema to compensate for. The description appropriately adds the only relevant scope detail, 'up to 50', without inventing parameter semantics.

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 verb and resource: read the newest owned website enquiries, with a cap of 50. This is clear enough to distinguish it from generic lead tools, but it does not explicitly name sibling alternatives such as soclo_leads_list or soclo_page_lead_handled.

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 implied by 'Read the newest owned website enquiries' and 'Free; changes nothing', giving context for a safe read operation. However, there is no explicit guidance on when to use this versus other lead or inbox listing tools, and no exclusions are stated.

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