get_blocked

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds non-obvious behavioral context by revealing that there are two distinct blocklists (story vs main) and that my_stories_from toggles between them. This goes beyond the annotated hints.

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 two short sentences, front-loaded with the core purpose and followed by the key parameter explanation. Every word is meaningful and there is no redundant content.

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 simple read-only list tool with complete annotations and an output schema, the description adequately covers purpose and the least obvious parameter. It lacks pagination details, but those are reasonably inferred from limit/offset and the existing output schema, making it sufficient for this complexity.

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 explicitly explains my_stories_from, which is the most cryptic parameter, adding value beyond the schema. However, limit and offset are left undocumented; while their names and defaults suggest pagination, the description does not confirm this or explain any interaction.

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 that the tool returns a list of blocked users. The clarification of my_stories_from (story-blocklist vs main) further specifies scope, and the tool name get_blocked distinguishes it from sibling actions like block_user and unblock_user.

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 explicit when-to-use or alternative guidance is provided. Usage is implied by the name and purpose, but the description does not mention exclusions or contrast with other tools. The parameter explanation hints at selecting between story and main blocklists, but no broader context is given.

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