seerr_get_user_settings_password

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

The readOnlyHint annotation already indicates a safe read operation, but the description adds no additional behavioral context. It does not disclose what data is returned, whether password hashes are exposed, or any sensitivity around user password information.

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 short but under-specified and contains a spelling error ('informatiom'). It reads more like a truncated phrase than a well-formed concise description, sacrificing clarity for brevity.

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?

Despite low complexity and the presence of an output schema, the description is too minimal. It doesn't explain what 'password page information' refers to, nor how this relates to the user_id parameter, leaving significant gaps for an agent.

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?

Schema description coverage is 0% and the description does not mention the user_id parameter at all. The description fails to compensate for the lack of parameter documentation, leaving the agent to guess the meaning of user_id.

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 states a verb ('Get') and a resource ('password page informatiom'), but 'password page' is ambiguous and typo-ridden. It doesn't clearly differentiate from sibling tools like seerr_get_user_settings_main or seerr_create_user_settings_password, though it implies a read operation on password-related settings.

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 given on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage solely from the name.

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