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

Annotations already declare this as a safe, read-only, idempotent, closed-world operation with no destruction. The description adds useful behavioral context by enumerating what the totals cover (status counts, enrichment progress, similar portfolio metrics), but it leaves the exact return shape vague and says nothing about freshness or scoping beyond 'the user's saved properties'.

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?

A single front-loaded sentence that describes the resource and its main aggregate categories. Every clause carries information; there is no padding or restatement of the tool name.

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 aggregate tool with no output schema, the description gives an agent enough to know it will receive portfolio-level summary counts rather than a list or single record. The only slight gap is that 'similar portfolio-level numbers' is fuzzy, but the key categories are named.

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 input parameters, so there is nothing for the description to explain. The baseline for a parameterless tool applies, and the description correctly does not invent parameter guidance.

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 output: aggregate totals for the user's saved properties, including counts by status and enrichment progress. It distinguishes itself from listing siblings like spur_list_saved_properties and from single-property spur_get_property by emphasizing portfolio-level numbers, though it does not name those alternatives explicitly.

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 rather than stated: an agent can infer this is the tool for portfolio summaries rather than raw lists or single-property details. However, there is no explicit when-to-use rule or mention of alternatives such as spur_list_saved_properties or spur_get_property.

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