Single tool 'beacon_feature' has a visible schema with 13 parameters, but critical gaps undermine quality. Description (127 chars) is present but vague, it lists actions without explaining WHEN to use each or what the tool returns. Parameters lack individual descriptions entirely (0/13 have descriptions per the schema). The schema shows types and enums for 'action' and 'status', but most parameters (title, id, category, priority, front, kind, layer, description, parentId, parentTitle, items, features, files, architecture) have no descriptions, violating the baseline that 100% of A+ tool params have descriptions. No output schema is documented. Error handling is absent from the visible code. The tool conflates multiple concerns (add, start, subtasks, done) into one dispatcher, violating single-responsibility. No evidence of idempotency, pagination, or recovery guidance.

• Add a description to every parameter. Format: 'Feature title (string, 1-200 chars, required for add/start actions)'. Include constraints, valid ranges, and when each param applies.
• Rewrite tool description to 50-150 chars answering: What does it do? When use it? What does it return? E.g. 'Manage feature lifecycle: create cards in BACKLOG, transition to IN_PROGRESS, add subtasks, mark DONE. Returns feature ID and updated status.'
• Document the output schema. Specify what fields are returned for each action (add, start, subtasks, done). Include feature_id, status, created_at, updated_at, etc.
• Split beacon_feature into 4 separate tools: create_feature (add), start_feature (start), add_feature_subtasks (subtasks), complete_feature (done). Each tool has one clear responsibility.
• Add error handling: return structured errors with actionable guidance. E.g. 'Feature not found (id=xyz). Check feature ID or call list_features() to find valid IDs.'