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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, matching the 'Returns' verb, so the safety profile is covered. The description adds that the response carries both 'content' and 'rulesRevision', which is genuinely useful given there is no output schema. It stops short of noting auth needs or any other behavioral trait, so it lands at a solid-but-not-rich 3.

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?

Effectively two sentences, front-loaded with the core verb and resource, with no filler or marketing prose. The parentheticals ('(content)', '(rulesRevision)') are dense but each carries information. Slightly run-on syntax keeps it from a 5.

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?

With no output schema, the description correctly compensates by naming the returned fields (content, rulesRevision). Both parameters are fully documented in the schema, and the task/work-type dependency is captured. What remains missing is explicit routing to the create tools this precedes, but the essentials for correct invocation are present.

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 description coverage is already 100%, which sets the baseline at 3, but the description goes further by stating the conditional relationship: 'For a task, the template depends on its work type.' This explains why taskType matters and why it is required only when entity is 'task', adding rationale beyond the schema's bare 'required when entity is task' note.

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 uses a specific verb ('Returns') and names the concrete resources: the workspace's conventions and description template plus its revision (rulesRevision). It is distinguishable from siblings like feature_create/task_create because the description makes clear this fetches the rules rather than creating anything. The nested phrasing ('for a new feature, task or bug (content)...') is slightly hard to parse, and the tool name 'create_rules' implies a mutation, which the description must and does correct.

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?

Usage is only implied: the phrase 'that creation requests carry' hints this is called before a create call, but the description never explicitly states when to use it versus siblings or names the alternative tool. No exclusions or prerequisites are given. An agent can infer the context but must do so itself.

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