sonarr_create_languageprofile

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

Annotations already convey readOnlyHint=false and destructiveHint=false. The description adds 'WRITE: this modifies your Sonarr instance,' which reiterates the write nature but provides no new behavioral details beyond annotations. It is not contradictory.

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 extremely concise: two short sentences with the primary action front-loaded. Every word earns its place and no redundant phrases are present.

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?

The tool handle is a create operation with an opaque body schema. The description omits any information about the body's required fields, default behavior, or how to discover the schema (e.g., via list_languageprofile_schema), making the tool difficult to use correctly.

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 a single 'body' object with no property descriptions and 0% schema description coverage. The description fails to mention the body parameter at all, leaving the agent without any guidance on required structure or fields.

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 'Create language profiles' with a specific verb and resource, distinguishing it from list/update/delete siblings. The 'WRITE' prefix reinforces the mutation intent.

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 description implies usage (use when you need a new language profile) but provides no explicit when/when-not guidance or references to sibling tools like update_languageprofile. No exclusions or alternatives are mentioned.

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