get_my_protocols

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

No annotations are provided, so the description must carry the burden. It implies read-only by saying 'Retrieve', but does not explicitly state non-destructive nature, authentication needs, or other behaviors. However, for a simple list retrieval, the implications are somewhat obvious. Adds minimal behavioral context beyond the verb.

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?

Two sentences, both efficient. First sentence states purpose, second provides guidance. No extraneous words.

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?

Tool has no parameters and an output schema exists (per context). Description is complete for a simple list retrieval: it covers purpose and usage guidance, with no obvious gaps given the simplicity.

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?

Input schema has zero parameters, so schema coverage is 100% and no parameter explanation is needed. Description adds no param info, but baseline for 0 parameters is 4; no additional value is expected.

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?

Description clearly states 'Retrieve basic information for all protocols belonging to the current user', which is a specific verb+resource. It also distinguishes from sibling tool get_protocol_steps by noting that tool provides detailed steps.

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?

Explicitly provides when-to-use (get basic info for user's protocols) and when-not (for detailed steps, use get_protocol_steps). Directs to an alternative tool, making usage context clear.

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