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

Annotations do not indicate side effects, and the description implies submitting a request but does not state what happens afterward, whether it creates a persistent record, or what response the caller should expect. No contradiction exists.

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 one focused sentence with no filler, front-loading the purpose and usage conditions efficiently.

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 7 parameters and an output schema, the description omits parameter meanings, return behavior, and side effects. It covers only selection criteria and the priority scale, which is too sparse for complete invocation guidance.

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?

Only priority is partially explained ('1-10, higher = more urgent'); title, description, use_case, node_type, workflow_id, and priority_justification are left undefined with 0% schema coverage. The description does not compensate for this gap.

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 the specific action 'Request a feature' for workflow building and lists concrete triggers (missing capability, unsupported workflow pattern, improvement), which clearly distinguishes it from siblings like report_bug.

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?

Explicitly says 'Use this when' and enumerates three scenarios, plus explains the priority scale. This gives clear selection guidance even without mentioning when not to use it.

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