telegram-get-paid-reaction-privacy

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description confirms it's a read operation by saying 'Get your current...', but adds no additional behavioral context beyond what annotations provide. No mention of authentication prerequisites or side effects, though none are expected for a getter.

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 sentence with no superfluous words. It is appropriately sized and front-loaded with the action and resource.

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 tool has no parameters and no output schema, the description is sufficient. It precisely states what is retrieved. Could potentially mention that it returns a boolean or setting value, but not strictly necessary for a simple getter.

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 zero parameters, and schema description coverage is 100%. The description adds no parameter details, but none are needed since there are no parameters. Baseline for zero parameters is 4.

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 the current default paid reaction privacy setting. The verb 'Get' and the specific resource 'default paid reaction privacy setting' are unambiguous, and it distinguishes itself from siblings like 'telegram-set-default-reaction' and 'telegram-toggle-paid-reaction-privacy'.

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 is clear about what it does, but does not explicitly state when to use this tool versus alternatives (e.g., 'telegram-get-global-privacy-settings'). However, the specificity of 'paid reaction privacy' makes the usage context obvious.

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