snw_list_derived_properties

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

No annotations are provided, so the description carries the behavioral burden. The verb 'list' implies a read-only operation and the phrase 'complete auditable semantic plan' hints at output scope, but the description does not disclose details such as pagination, depth, or whether execution is triggered. Still, the read-only nature is reasonably inferable.

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 sentence that front-loads the action and resource, then adds one meaningful qualifier about the semantic plan. There is no redundancy or filler.

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?

Given that the tool has no parameters and an output schema exists, the description sufficiently conveys what the tool returns and its general purpose. It does not need to explain return values in detail. However, it does not mention how this listing relates to sibling list tools, which is a minor gap.

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 parameters enforce, so the description does not need to document parameter details. The baseline for zero-parameter tools is 4, and the description does not introduce any confusion.

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 verb ('列出'/'list') and a clear resource ('created derived properties'), and adds that it returns the complete auditable semantic plan. This distinguishes it from siblings like snw_create_derived_property and snw_execute_derived_property, which are clearly different operations.

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 gives no guidance on when to choose this tool over alternatives such as snw_execute_derived_property or snw_analyze_field_request. It implies a listing use case but does not state exclusions or conditions for preferring a sibling.

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