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

Though annotations already mark it read-only and idempotent, the description adds key behavior: it requires an agency API key, returns only own properties, orders newest first, and clarifies status semantics (e.g., 'draft' includes new + in review). This goes beyond the annotations and gives necessary context for correct invocation.

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 compact two-sentence statement that integrates purpose, usage, auth, and scope without redundancy. The ordering constraint and filtering options are front-loaded, making it easy for an agent to parse quickly.

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 read-only listing tool, all needed information is present: auth requirement, scope, ordering, and filter options. The default limit is in the schema, and no output schema is required for a list operation. Nothing critical is missing.

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?

Status and reference have explicit descriptions, and the enum values with explanations (especially 'draft' and 'all') are helpful. The limit parameter lacks a prose description, but its minimum, maximum, and default are self-explanatory from the schema. Overall, parameter meaning is clear despite 67% coverage.

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 tool lists the calling agency's own property listings, newest first, with optional status/reference filters. This is distinct from siblings like search_properties (general search) and get_property (single property), and the scope is explicitly limited to own listings.

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 concrete usage examples ('show my listings', 'is reference X still online?') and notes the agency API key requirement, which implies it is for agency-specific queries. It does not explicitly name alternatives or say when not to use it, but the scope statement effectively excludes general searches.

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