obs-get-profile-list

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

No annotations are provided, so the description carries full burden. 'Gets an array' implies a read-only operation, but it doesn't disclose whether this requires specific permissions, if it's cached or real-time, what happens when no profiles exist, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place by conveying essential information without 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?

For a simple read-only tool with 0 parameters and no output schema, the description is minimally adequate. It states what the tool does but lacks behavioral context (permissions, performance, error cases) and usage guidance. Without annotations or output schema, the agent must infer details from the name and sibling tools, leaving room for uncertainty.

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 0 parameters with 100% schema description coverage, so the schema already fully documents the absence of inputs. The description doesn't need to add parameter details, but it correctly implies no filtering or options are available (just 'all profiles'), which aligns with the empty schema. Baseline for 0 params is 4.

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 'Gets an array of all profiles' clearly states the action (gets) and resource (profiles), making the purpose immediately understandable. It distinguishes from siblings like 'obs-get-profile-parameter' (specific parameter) or 'obs-set-current-profile' (mutation), but doesn't explicitly contrast with other list-retrieval tools like 'obs-get-scene-list' or 'obs-get-input-list'.

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?

No guidance is provided on when to use this tool versus alternatives. While the name implies it retrieves all profiles, there's no mention of whether this should be used for enumeration, selection, or as a prerequisite for other operations like 'obs-set-current-profile'. The description doesn't help the agent decide between this and other 'get' tools in the sibling list.

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