get-user-room-subscription-settings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get', implying a read-only operation, but doesn't specify permissions required, rate limits, error conditions, or what the return data looks like. For a tool with no annotation coverage, this is a significant gap in transparency.

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, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core purpose without unnecessary elaboration, making it easy for an agent to parse quickly.

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?

Given the complexity of a user-specific settings retrieval tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks details on authentication, response format, error handling, and how it differs from similar sibling tools, making it inadequate for reliable agent use.

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 description mentions 'user's room subscription settings', which implies the 'userId' parameter is needed to identify the user, adding some semantic context beyond the schema's 0% description coverage. However, it doesn't clarify the format or constraints of 'userId' (e.g., whether it's an email, ID, or something else), so it only partially compensates for the lack of schema documentation.

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 verb 'Get' and the resource 'user's room subscription settings', making the purpose specific and understandable. However, it doesn't distinguish this tool from its sibling 'get-room-subscription-settings', which appears to be a similar tool without the user focus, leaving room for confusion about when to use one versus the other.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get-room-subscription-settings' and 'update-room-subscription-settings' present, there is no indication of prerequisites, context, or distinctions, leaving the agent to infer usage based on tool names alone.

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