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

Annotations already indicate readOnlyHint, and the description adds context about requiring project context. It does not disclose possible failure modes (e.g., 404 if not found), but given the annotation coverage, the bar is lower and the added context is useful.

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 concise and effective, using two sentences to convey the operation, returned fields, and a prerequisite. No redundant or vague wording.

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?

Provides enough context by listing the returned fields and the project context requirement. Without an output schema, this is helpful. It could mention error cases or explicitly reference list_tags, but the information given is adequate for a single-get operation.

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 covers all parameters with descriptions, so baseline is 3. The description does not add parameter-specific semantics beyond what the schema provides, but it gives overall context about the returned fields.

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 it retrieves a single endpoint tag and lists the returned fields. It is specific about the operation, though it could more explicitly contrast with list_tags for batch retrieval.

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?

Mentions a prerequisite ('Requires project context') but does not explicitly guide when to choose this over alternative tools like list_tags. The intent is reasonably clear from the name but lacks explicit when/when-not guidance.

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