get_workflow_rules

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope. The description adds that the returned rules are evaluated for the calling agent, which is genuinely useful context, but it says nothing about freshness, caching, or failure modes.

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?

A single front-loaded sentence with a verb-first construction and a compact enumeration of return contents. No filler and nothing repeated from the name.

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 partially compensates by naming the returned categories (transitions, policies, permissions). However, for a read-only tool sitting among several near-identical rule tools, the absence of any disambiguation leaves ambiguity about when this is the correct call.

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 is a single parameter (project_id) with 100% schema description coverage, so the schema carries the parameter burden and baseline 3 applies. The description adds no format or scope detail for the ID beyond what the schema already states.

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?

Specific verb+resource ('Get workflow rules for a project') with an enumeration of what the rules cover (transitions, policies, permissions). However, it fails to distinguish itself from close siblings such as get_project_rules, get_assignment_rules, and get_my_rules, which an agent could easily confuse it with.

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?

No when-to-use guidance is given. The phrase 'for the calling agent' hints at per-agent scoping, but there is no explicit condition, prerequisite, or alternative named despite three similarly-named rule-retrieval siblings in the toolset.

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