Get a tag

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

Without annotations, the description must disclose behavior. It states the tool fetches a single tag, which implies a read operation, but does not address error conditions (e.g., missing tag), rate limits, or whether the operation is safe. The description is adequate but not comprehensive.

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 exceptionally concise, consisting of two short sentences that convey the essential information without any superfluous 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?

Given the low complexity (two optional parameters, no output schema, no nested objects), the description covers the core behavior and constraint. It could mention what happens if both or neither parameter is provided, but overall it is sufficient for an agent to use the tool correctly.

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, the description compensates by clarifying that the two parameters are mutually exclusive ('by id or slug') and that exactly one must be provided. However, it does not specify constraints like valid formats or required presence, leaving some ambiguity.

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 'Fetch a single tag by id or slug', specifying the verb, resource, and identifier options. It effectively distinguishes from sibling tools like ghost_list_tags which lists tags, and ghost_get_post which fetches a different resource.

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 instruction 'Provide exactly one' is helpful but lacks explicit guidance on when to use this tool versus alternatives such as ghost_list_tags. There is no mention of prerequisites or context for choosing id over slug.

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