get_property_details

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

With no annotations, the description must carry behavioral disclosure. It implicitly signals a read-only lookup and usefully enumerates the fields returned, which is real behavioral value. However, it says nothing about error behavior for an invalid/missing property, permission requirements, or rate limits.

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 with the verb and the returned-field list; every word earns its place with no preamble or redundancy.

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 exists, so the description usefully compensates by listing the returned fields. Combined with a fully documented single parameter, this is nearly complete for a simple read tool; only edge-case behavior (missing property, auth) is unaddressed.

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 coverage is 100% and there is only one parameter, whose accepted formats and discovery path are fully documented in the schema. The description adds no additional meaning about property_id, so the baseline 3 applies.

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?

States a specific verb+resource ('Return details about a property') and enumerates the returned fields (time zone, currency, industry, service level, create time), so the agent knows exactly what this yields. It doesn't explicitly differentiate itself from siblings like get_account_summaries, but those operate on a different resource, so confusion risk is low.

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?

No when-to-use guidance, no prerequisites, and no alternatives named. The useful routing hint ('Use get_account_summaries to find it') lives in the schema's property_id description, not in the tool description, so the description itself offers no selection help.

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