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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description goes further by disclosing the return structure (status columns and per-card fields), which is behaviorally useful and not present in the structured data.

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?

Two densely informative sentences, front-loaded with the resource identity before the purpose. Every clause earns its place by describing columns, fields, or intent.

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 compensates by describing the returned kanban shape. Annotations cover safety, parameters are fully documented in the schema, and no behavioral gap remains for correctly invoking this read-only board.

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 100% so the two filters are already documented. The description adds marginal value by naming working group and category as card attributes, implicitly confirming what the filters operate on, but does not explain filter syntax.

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 (Get) plus a precisely named resource (RADIX Wiki Ideas Pipeline kanban) and scope. It enumerates the status columns and card attributes, so an agent knows exactly what this returns and how it differs from the page-oriented siblings.

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?

"Use this to follow DAO / project progress" gives clear usage context, and no sibling offers an equivalent kanban view. However, it does not state when-not to use it or name an alternative for narrower page lookups.

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