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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds that results include schedule, filters, and run timestamps, but it does not describe ordering, pagination, or whether all automations are returned.

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 single compact phrase with no redundancy. It front-loads the core resource and then lists the relevant returned fields.

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 list with comprehensive annotations, the description covers the key returned data. It leaves minor gaps around result ordering and pagination, but the tool is simple enough that these are not critical for invocation.

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?

There are no input parameters, so there are no parameter semantics to explain. The baseline of 4 applies because the schema requires no additional description.

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 identifies the resource as scheduled property searches and enumerates the returned details (schedule, filters, next/last run times), so an agent can distinguish this listing from creation or execution siblings. It does not open with an explicit list verb, but the title and content make the operation clear.

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?

There is no explicit guidance on when to use this tool versus alternatives such as spur_create_search_automation or spur_run_search_automation. The usage is only implied by the phrase 'Scheduled property searches with...'.

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