obs-get-source-private-settings

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about permissions, whether private settings are sensitive data, or what the call returns. Only the implicit 'Gets' signals that this is a read operation.

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?

It is a single short sentence with no wasted words, but the brevity reflects under-specification rather than efficiency. Nothing is front-loaded beyond the bare purpose.

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 two optional, unannotated parameters, no output schema, and no explanation of the sourceName/sourceUuid relationship, the definition leaves real ambiguity for the caller. For a lookup tool against a complex OBS API, an agent needs more than a restated name.

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%, so both sourceName and sourceUuid are already documented in the schema. However, the description adds nothing about how the two optional identifiers relate (whether they are alternatives or precedence rules), so it does not improve on the schema baseline.

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 sentence 'Gets the private settings of a source' essentially restates the tool name (obs-get-source-private-settings) with no added specificity. It does not distinguish this from the sibling obs-get-scene-item-private-settings or clarify what 'private settings' means for an OBS source.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as obs-get-input-settings or obs-set-source-private-settings. The agent must infer usage entirely from the name.

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