get_propertysources

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

The description adds no behavioral context beyond what the annotations already declare. Annotations indicate this is read-only, idempotent, non-destructive, and open-world, but the description does not mention pagination behavior, result bounds, or whether disabled/hidden PropertySources are included.

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 undeniably short and front-loaded with no fluff. However, it under-specifies rather than being merely concise, since it provides no scope, filter guidance, or differentiation from related tools.

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?

With no output schema and five filter/pagination parameters, the description is too thin to fully contextualize the tool. It does not describe the return shape, the meaning of a PropertySource in this domain, or how the list relates to the singular `get_propertysource` tool.

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 100%, and each parameter already has a meaningful description, including an example for `filter`. The tool description adds no parameter-level insight, so the baseline of 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?

The description states a verb ('List') and a resource ('PropertySources'), so it is recognizable as a list operation. However, it mostly restates the tool name and does not clarify what a PropertySource is or how this differs from the singular `get_propertysource` sibling, leaving the purpose minimally informative.

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 guidance about when to use this tool versus `get_propertysource` or the create/update/delete/import PropertySource tools. It also does not explain when the filter parameters should be used versus the simpler name filter, so an agent gets no selection or invocation guidance from the description.

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