obo-mcp

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

No annotations provided, so description carries full burden. Mentions data source 'index.json' and explains business logic for 'incomplete' status filtering. Missing safety/disposition info (read-only implied by 'List' but not stated), error handling, or performance characteristics.

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?

Efficiently structured with purpose statement followed by Args block. No redundant sentences. The docstring-style 'Args:' format is slightly technical but serves the same function as front-loaded narrative without excessive verbosity.

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?

Adequate for a listing tool with output schema present (no return value explanation needed). Covers input parameters well given zero schema coverage. Could be improved by clarifying relationship to session management workflow and other list operations.

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?

Excellent compensation for 0% schema description coverage. Documents both parameters: base_dir as 'Project root directory' and status_filter with valid enum values ('active', 'completed', 'incomplete') plus behavioral definition of 'incomplete'. Adds significant value beyond the raw schema types.

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?

States specific verb ('List') and resource ('OBO sessions') with data source ('index.json'). Clearly distinguishes from sibling obo_list_items by targeting sessions rather than items, though it doesn't explicitly reference the sibling differentiation in text.

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?

Provides implicit usage guidance by defining filter values ('active', 'completed', 'incomplete') and explaining the semantics of 'incomplete' status. However, lacks explicit when-to-use guidance relative to siblings like obo_session_status or obo_list_items.

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