Pilot MCP

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

With no annotations provided, the description carries the full burden but adds minimal behavioral context beyond 'full' implying complete retrieval. It does not explain what data structure is returned, whether it includes metadata/attachments, or how the target note is determined without parameters.

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?

While brief (3 words) and front-loaded, the extreme brevity becomes a liability given the confusing empty schema. The single sentence does not earn its place by resolving the critical ambiguity of how this tool identifies which note to read.

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 zero parameters, no annotations, and no output schema, the description needed to explain the selection mechanism (e.g., reading a 'current' note) and return format. It leaves critical operational questions unanswered, making it inadequate for agent invocation.

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?

Per scoring rules, 0 parameters establishes a baseline of 4. The description neither adds nor detracts from this baseline since it correctly omits parameter discussion (as there are none), though it fails to address the ambiguity of how note selection occurs.

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 the verb (Read) and resource (note) with scope (full content), but is somewhat tautological ('read_note' → 'Read full note content'). Critically, it fails to explain how to specify which note to read given the empty parameter schema, nor does it distinguish from sibling search_notes or list_notes.

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 absolutely no guidance on when to use this tool versus siblings like search_notes or list_notes. No mention of prerequisites, required context, or selection criteria given the lack of input parameters.

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