mdl_account_get_privacy

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is largely covered. The description adds the specific endpoint and return field (profile.read.feeds) with failure code -2 and notes the authentication requirement, which is useful behavioral context beyond annotations, but doesn't elaborate on error handling beyond the one code or rate limits.

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?

One compact sentence front-loads the purpose, endpoint, return field, failure indicator, and auth requirement. Every element earns its place with no waste.

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 read-only endpoint with no parameters and full annotation coverage, the description supplies essential endpoint and return details. However, it doesn't explain what 'profile.read.feeds' represents semantically or how the tool fits with related account tools, leaving some contextual gaps.

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?

With zero parameters, the baseline is 4. The description doesn't need to add parameter meaning, and appropriately doesn't.

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?

States a specific verb+resource: 'Account: get privacy', mapping to the GET /users/settings/privacy endpoint. It's clear what the tool retrieves and distinct from siblings like mdl_account_update_privacy, though it could explicitly differentiate from related account endpoints.

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 mention that it requires host-configured authentication implies a usage context, but there's no explicit when-to-use or when-not-to-use guidance versus related tools such as mdl_account_get_profile or mdl_account_get_activities.

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