create_propertysource

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

Annotations already indicate write operation (readOnlyHint false) and non-idempotent (idempotentHint false). The description adds value by specifying permission requirements and the accepted format, and notes that overwrite can delete an existing PropertySource (implied by the overwrite parameter in schema). No contradiction with annotations.

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?

Three concise sentences, front-loaded with the core purpose, followed by usage guidance and alternative. No fluff 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?

Given the schema fully documents parameters and annotations cover basic flags, the description is sufficient for an agent to decide when to use and what format to provide. It lacks explicit mention of return values or error behavior, but these are not critical for a create operation without an output schema.

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 covers both parameters (definition and overwrite) with descriptions, so baseline is 3. The description adds a hint about the definition format ('full definition dict' in REST API format), which slightly enhances understanding but is not essential given 100% schema coverage.

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?

Clear verb 'Create' with resource 'PropertySource' and explicit format specification (REST API format). It distinguishes from import_propertysource, which uses LM Exchange format, and references export_propertysource output, making the purpose unambiguous.

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?

Explicitly states when to use (round-tripping exports or building from scratch) and provides an alternative (import_propertysource for LM Exchange). Also notes the required write permission, guiding the agent on prerequisites.

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