get_annotation

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

With no annotations, the description carries the full behavioral burden, but it only implies a read operation through the verb 'Get' and notes a version requirement. It does not disclose required permissions, behavior when the annotation is missing, whether the response is cached, or other operational traits.

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 filler. However, its brevity reflects under-specification rather than fully earned conciseness, since useful context could have been added without bloat.

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 ID-based retrieval tool with no output schema and no annotations, the description is too sparse. It identifies the resource and a version compatibility note but omits usage boundaries, parameter meaning, return expectations, and permission or error behavior.

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?

Both required parameters have 0% schema description coverage, and the description does not mention websiteId or annotationId at all. The parameter names are present in the schema, but the description adds no meaning about scoping, valid values, or lookup behavior.

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 states a specific verb and resource: 'Get a website annotation'. It is clear that this retrieves one annotation, but it does not explicitly distinguish the operation from sibling reads such as list_annotations or explain the ID-based lookup.

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 provides no guidance on when to use this tool versus alternatives. It does not mention list_annotations, prerequisites, permissions, or error conditions, leaving usage entirely implied by the tool name.

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