pm_meta

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

No annotations provided, but the description declares read-only and describes the return format (arrays of id+name pairs). This is sufficient for a simple list operation; no side effects mentioned, but none expected.

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?

Three short sentences with no redundancy. The main action is front-loaded, and every sentence adds essential information.

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?

Given no parameters and no output schema, the description covers the tool's purpose, behavior, and usage context completely. It leaves no ambiguity about what the tool returns or when to use it.

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?

No parameters exist, baseline 4. The description adds value by explaining the output format (id+name pairs) which aids understanding of the tool's function.

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 clearly states it lists PM metadata (lists, statuses, members, features) as id+name pairs. It uses a specific verb ('List') and resource, and distinguishes itself from sibling tools which focus on tasks, conversations, etc.

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 to call before create_task / update_task for name-to-id resolution, and warns not to guess an id. This provides clear when-to-use guidance and an exclusion.

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