Список вложений

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

No annotations provided; description only states read-like behavior (returns), but doesn't disclose side effects, permissions, or pagination behavior (though limit parameter suggests pagination is not explained).

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?

Single sentence, no fluff. Front-loaded with the main purpose. Could benefit from slight expansion but remains concise.

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 listing tool with two parameters and no output schema, the description is too brief. Lacks details on return structure (e.g., file names, sizes) and does not compensate for missing parameter documentation.

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 50% (pageId documented, limit undocumented). Description does not add any parameter details beyond schema, leaving limit parameter unexplained.

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 returns page attachments with download links. It distinguishes from sibling tools like upload_attachment and download_attachment, but lacks specificity about what information is included.

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 on when to use this tool versus alternatives (e.g., download_attachment for single files). No context about prerequisites or typical use cases.

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