get_notes

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

No annotations are provided, so the description must disclose behavioral traits. It only implies read-only behavior through 'Retrieve', but does not explicitly state that it doesn't modify data, nor does it mention authentication needs, rate limits, or any side effects.

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 concise with a brief purpose line followed by a parameter list. It's front-loaded and each sentence is useful. Minor improvement could be more structured formatting, but overall efficient.

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 existence of an output schema (not shown), the description doesn't need to detail return values. However, it lacks information on ordering, date range inclusivity, and behavior when 'id' is combined with other filters. Adequate but with clear gaps.

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 adds significant value: it lists enum values for 'note_type', specifies date format YYYY-MM-DD, and gives a default for 'limit'. This meaningfully augments the bare schema.

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 'Retrieve notes' with a parenthetical listing of note types, identifying the specific verb and resource. The sibling tools (e.g., get_metrics, get_workouts) are distinct, so this tool is well-differentiated.

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 sets clear context: it's for retrieving notes with optional filters. It doesn't explicitly state when not to use it or mention alternatives, but the sibling tools cover different resources, so usage is implied correctly.

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