Markplane provides 5 tools with explicit JSON Schema input definitions visible in crates/markplane-cli/src/mcp/tools.rs. All tools have descriptions and schema structures. However, there are notable gaps: (1) Tool names lack action verbs, 'markplane_summary', 'markplane_query', 'markplane_show', 'markplane_add', 'markplane_update' are prefixed but not verb-first, which slightly delays LLM parsing; (2) Output schemas are not documented, the code shows input schemas but does not specify what fields each tool returns, forcing LLMs to infer structure; (3) Parameter descriptions are present but inconsistent in detail, some are thorough (e.g. priority with enum hints), others minimal (e.g. 'id' in markplane_show has only 'Item ID (e.g. TASK-042, EPIC-001, PLAN-003, NOTE-007)'). (4) Error handling is absent from visible code, no recovery guidance or actionable error messages shown. The schema quality is solid for a READ_ONLY project tool, but lacks the polish and completeness expected for production agent interaction.

• Rename tools to action-verb-first: 'get_project_summary', 'list_items', 'get_item_details', 'create_item', 'update_item'. This lets LLMs infer intent from the name alone.
• Document output schemas for all 5 tools. Define the response structure: e.g. 'markplane_query returns { items: [{id, title, status, priority, ...}], total: number, nextCursor?: string }'.
• Add limit and offset (or cursor) parameters to markplane_query to support pagination. Default limit=20, max limit=100. State this in the description.
• Convert priority, kind, status, effort, type, note_type parameters to JSON Schema enums instead of describing allowed values in text. This enables LLM auto-completion and validation.
• Add error response examples and recovery guidance to tool descriptions. E.g. 'If the item is not found, try markplane_query() to search by filters.'
• Specify which fields are returned by each tool. E.g. 'markplane_show returns {id, title, status, priority, effort, assignee, tags, created, updated, body}'. Helps LLMs chain tools.
• For markplane_add and markplane_update, clarify which parameters are mutually exclusive or dependent. E.g. 'effort only applies to tasks; note_type only applies to notes.'
• Add confirmation/dry-run support for markplane_add and markplane_update (destructive writes) to prevent accidental changes. E.g. add a 'dryRun' boolean parameter.