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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the data comes from the DB with no markdown, and the payload carries verification_strategy (auto|manual), which tells the agent what it can act on. Minor gap: no pagination or volume hints.

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?

Three dense sentences with the resource and scope front-loaded, followed by parameter format and usage. Every sentence adds information, though the parenthetical notation examples make it slightly packed rather than maximally clean.

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, no-output-schema fetch, the description covers what is returned (lifecycle_fields, verification_strategy), its source (DB, no markdown), and the calling workflow. An agent has enough to invoke it correctly; only return shape details are absent.

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 coverage is 50% and the two ID parameters are undocumented in the schema, so the description carries that burden: it specifies bare ordinals as canonical, allows prefixed forms (TS-107, #US-12), and clarifies both lists are optional ('and/or'). This meaningfully exceeds the schema. botId/projectApiKey semantics still live in the schema descriptions.

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?

States a specific verb (Fetch) and resource (lifecycle_fields for user stories and/or test scenarios), plus a scope qualifier (DB only; no markdown) that separates it from sibling readers like get-user-stories and get-test-scenarios, which return the entities themselves. An agent can tell what this returns without opening the schema.

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?

Gives an explicit trigger and downstream workflow: 'Use after identifying scenarios in scope for create-tests to read verification_strategy (auto|manual) and skip manual ones.' That is clear when-to-use context, though it names no alternative tool for the case where the caller needs different data.

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