Semaphores

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by explaining that a semaphore at max holders means jobs are queued, which provides behavioral context beyond annotations. It does not contradict any 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 concise with three sentences plus an Args block. The first sentence states purpose, the second gives usage context, and the third explains a key detail. No unnecessary information.

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?

The tool has an output schema (not shown) and one optional parameter. The description covers the tool's purpose, usage scenario, parameter semantics, and behavioral nuance. It is complete for a list 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?

The input schema has 0% description coverage, but the description compensates by documenting the 'tenant' parameter: 'Tenant name (uses default if empty).' This clarifies behavior, which is absent from the schema.

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 'List semaphores — resource locks that limit concurrent job execution.' This specifies both the action (list) and the resource (semaphores), and distinguishes this tool from sibling list tools by explaining the semantic meaning of semaphores.

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?

Explicit guidance: 'Check this when jobs are waiting unexpectedly.' This tells the agent when to use the tool. While it doesn't explicitly state when not to use it or list alternatives, the context is clear and sufficient for an AI agent.

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