obo-mcp

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation via the word 'Return,' but does not disclose idempotency, error behavior (e.g., what happens if session_file doesn't exist), performance characteristics, or what specific statistics are included in the summary.

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?

The description is optimally concise with zero wasted words. It front-loads the purpose statement and uses a structured Args section to document parameters efficiently. Every sentence earns its place.

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 the presence of an output schema (which obviates the need to describe return values) and the description's coverage of both parameters, the definition is adequately complete for a simple retrieval tool. It could be improved by mentioning error handling for missing files.

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?

With 0% schema description coverage, the description fully compensates by documenting both parameters in the Args section: session_file's path resolution logic (absolute vs. relative to {base_dir}/.github/obo_sessions/) and base_dir's conditional requirement. This adds essential meaning missing from the schema titles.

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 states the tool 'Return[s] summary statistics for an OBO session,' providing a clear verb and resource. However, it does not explicitly differentiate from sibling tool obo_list_sessions, which also deals with sessions but returns a list rather than statistics for a specific session file.

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?

The description provides no guidance on when to use this tool versus alternatives like obo_list_sessions or obo_get_item. There are no prerequisites, conditions, or workflow context provided to help the agent select this tool appropriately.

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