check_rule_publish_status

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

Lacks annotations; the description is ambiguous about side effects. The bullet 'If not published → publish the rule' suggests a write operation, but the tool name and return type imply read-only. No disclosure of actual behavior.

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 structured with bullets and an Args section, but includes verbose workflow instructions that are not part of the tool's direct behavior, reducing conciseness.

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?

Does not describe the return dict structure, error cases, or side effects. For a simple tool with no annotations or output schema detail, the description is incomplete.

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?

With 0% schema description coverage, the description explains 'rule_name: Name of the rule to check'. This adds basic meaning beyond the schema's type-only definition, but is minimal.

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 states 'Check if a rule is already published' which is clear, but then includes workflow steps that suggest the tool may also publish or prompt the user, creating ambiguity about the tool's core function.

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 guidance on when to use this tool vs siblings like 'publish_rule' or 'check_rule_status'. The workflow steps imply subsequent actions but do not explicitly differentiate.

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