Hide source

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the literal action without revealing side effects, such as whether the hide is per-scene, persists, or can be reversed by show_source.

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 plus an example, which is maximally concise and front-loaded. Every word contributes to conveying the core 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?

For a simple tool, the description is minimally viable but leaves out important contextual relationships with sibling tools (e.g., show_source) and does not compensate for the absence of parameter documentation. The existence of an output schema reduces the need to describe return values, so this is a marginal pass.

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 input schema has 0% description coverage, and the description does not explain the two parameters beyond what their names already imply. The phrase 'in a scene' adds no meaning to scene_name, and source_name is left entirely undeveloped.

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 clearly states the action ('Hide') and the resource ('a source in a scene'), which unambiguously distinguishes it from siblings like show_source or mute_source. The example 'Turn off my webcam' reinforces the intended behavior.

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 example provides a concrete use case, implying when to use this tool, but the description does not explicitly contrast it with alternatives such as show_source or set_source_visibility_in_all_scenes. There is no mention of when not to use it.

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