Shepherd MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a list operation but doesn't describe what 'list all' means in practice (pagination behavior, default ordering, what fields are returned, or any limitations). For a list tool with no annotations, this leaves significant behavioral questions unanswered.

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?

Extremely concise - just one sentence that serves two purposes: deprecation warning and functional description. Every word earns its place, and the critical deprecation information is front-loaded with brackets.

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?

For a simple list tool with one documented parameter and no output schema, the description provides minimal but adequate context about what the tool does and its deprecation status. However, it lacks information about return format, pagination, or any behavioral constraints that would be helpful for an agent.

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 description coverage is 100%, so the schema already documents the single 'limit' parameter. The description doesn't add any parameter-specific information beyond what the schema provides. Baseline 3 is appropriate when the schema does the documentation work.

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 the verb ('List') and resource ('all AI agent sessions from Shepherd'), making the purpose understandable. However, it doesn't distinguish this tool from its many siblings beyond the deprecation note, which slightly reduces clarity for current usage.

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 explicit guidance on when NOT to use this tool ('[Deprecated: Use aiobs_list_sessions]'), naming a specific alternative. This is perfect guidance for tool selection, even though it's negative guidance.

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