vibemap_list_features

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

Annotations already indicate the tool is read-only and non-destructive. The description adds that results are paginated and supports filtering, which provides additional useful context but does not go into deeper behavioral details like sorting or rate limits.

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 sentences with efficient placement of the core purpose first and supporting details second. No unnecessary words; every sentence adds value.

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?

Despite having 7 parameters and no output schema, the description only covers filtering and pagination. It does not describe the structure of returned data (e.g., which fields are included), which is a gap for comprehensive understanding. Adequate but not fully complete.

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 0%, so the description bears full responsibility. It explains filtering by status, priority, category, and search, and mentions pagination (limit/offset). While it doesn't describe each parameter in detail, it adds meaning beyond the raw schema, especially for the enum-based filters.

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 'List features for a VibeMap project,' using a specific verb and resource. It distinguishes from sibling list tools (e.g., vibemap_list_projects, vibemap_list_user_stories) by explicitly targeting 'features'.

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?

It provides clear context on when to use the tool, mentioning filtering capabilities and pagination. However, it does not explicitly state when not to use it or compare to alternatives, though the uniqueness of the purpose makes exclusions less critical.

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