voicebox_get_profile

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 states the tool returns 'detailed information' including specific items, but does not mention error handling (e.g., if profile_id is invalid), read-only nature, or any side effects. Basic transparency is present but insufficient.

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?

Two sentences with no extraneous words. The first sentence states purpose, the second enumerates key contents. Well-structured and front-loaded.

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 getter with an output schema, the description is mostly complete, covering the main purpose and contents. It lacks details on error conditions or specificity about which metadata is returned, but given the output schema existence, this is acceptable.

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 schema description for profile_id is minimal ('The profile ID.'), and the tool description adds context by stating what information the returned profile includes. However, it does not elaborate on the parameter itself beyond the schema. Given 100% schema coverage, the baseline is 3, and the description adds marginal value.

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 tool retrieves detailed information about a voice profile, listing included items (profile settings, sample count, metadata). It distinguishes from siblings like voicebox_list_profiles (which presumably lists all profiles without details) and more specific getters like voicebox_get_profile_channels.

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 (e.g., voicebox_list_profiles for listing, voicebox_get_profile_channels for channels only). There is no mention of prerequisites, such as requiring the profile to exist, or scenarios where this tool should not be used.

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