list_property_annotations

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

No annotations provided, and the description does not disclose any behavioral traits beyond returning annotations. Missing details on pagination, permissions, or side effects. The description minimally adds 'returns annotations' without depth.

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?

Description is five sentences, front-loaded with core purpose. Could be slightly more concise, but no unnecessary content. Structured with a clear separation between purpose, usage context, and parameter details.

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?

No output schema provided, but the description does not explain what the returned annotations contain (e.g., fields, pagination). Only states 'returns annotations', leaving the response structure undefined. Insufficient for an agent to fully understand the tool's output.

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?

Schema description coverage is 0%, but the description adds meaning to the single parameter 'property_id' by specifying accepted formats (number or string with 'properties/' prefix). This compensates for the schema's lack of 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?

Clearly states 'Returns annotations for a property' and explains what annotations are used for. Differentiates from sibling tools like get_property_details or run_report which serve different purposes.

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?

Provides context about when annotations are typically used (recording service releases, marketing campaigns, etc.), implying its use case. Does not explicitly state when not to use or alternatives, but the tool is the only one for annotations, making selection straightforward.

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