get_annotation_screenshotsReturn the region screenshots attached to an annotation as viewable images, so you can see exactly what the reporter pointed at.
| Name | Required | Description | Default |
|---|---|---|---|
| annotation_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| screenshots | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description aligns with annotations (readOnlyHint) and adds context about the images being 'viewable' and showing 'exactly what the reporter pointed at'. No contradiction; the description enriches understanding of the tool's behavior beyond annotations.
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, front-loaded sentence with no extraneous words. It efficiently states the action, resource, and benefit.
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 retrieval tool with output schema, the description covers the core purpose but omits parameter details. Given some context signals (e.g., no nested objects), the description is partially complete but lacks guidance on parameter semantics.
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 0% schema description coverage and one required parameter (annotation_id), the description does not explain the parameter's format, constraints, or source. It only mentions 'annotation' in the context, leaving the agent to infer the parameter's role.
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 region screenshots attached to an annotation as viewable images, with a specific verb 'return' and resource 'screenshots attached to an annotation'. It distinguishes from siblings like get_annotation by focusing on visual evidence.
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 implies when to use (when needing to see screenshots) but provides no explicit guidance on alternatives or when not to use. Siblings like get_annotation might also contain image references, but no comparison is offered.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of annotation or project management. Complementing pairs like diagnose_annotation vs. generate_prompt and get_annotation_analysis vs. diagnose_annotation are clearly differentiated by descriptions. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_annotations, create_github_issue, get_activity). Verbs like get, list, create, add, update are used systematically, ensuring predictability.
With 17 tools, the server covers annotation operations, project metrics, comments, GitHub integration, and sharing without being overwhelming. The scope is well-scoped for a specialized feedback/annotation tool.
Core annotation workflows (list, get, update status, comment, diagnose, generate prompt, create issues) are covered. Missing annotation creation, deletion, and detail updates are minor gaps given the server's focus on post-creation analysis and workflow.