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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context about what the response will contain, including limitations and compensation details, which goes beyond the annotations. It also sets an expectation that this is a safe, low-risk call to make first.

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 compact despite enumerating many specific content areas. It leads with the operation, then summarizes the return payload, and ends with actionable usage guidance. Every clause contributes meaningful information, and the single-sentence structure remains scannable.

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 read-only, parameterless tool with no output schema, the description fully equips an agent to decide when to call it. It explains what the machine-readable output covers, why it should be called first, and how it relates to subsequent searching. No important decision-making information is missing.

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?

There are zero parameters and the schema thoroughly documents this via an empty properties object and no required fields. The description reinforces that the tool needs no input and can be called unconditionally, which is appropriate at the baseline for a parameterless tool.

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?

Purpose is explicit: "Read a machine-readable description of Taskin," with a precise inventory of the content returned (capability groups, participants, geographic coverage, required fields, compensation, limitations). It differentiates from sibling tools by instructing to call it before searching, marking it as a discovery/overview tool distinct from task-status and submission tools.

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 gives clear guidance on when to call: "Call this first if you have not used Taskin before, or to check whether a category of work is in scope before searching." It does not explicitly name the sibling alternatives or state when not to use it, but the search reference and first-call instruction make the intended context unmistakable.

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