search_notes

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

The description only states it searches notes based on a query, with no disclosure of read-only behavior, pagination, or rate limits. Since no annotations are provided, the description fails to convey key behavioral traits.

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?

One sentence, no waste, but too minimal to be useful. Lacks structure or prioritization of key information.

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?

With 10 parameters, nested input, no output schema, and no annotations, the description is severely incomplete. It does not explain pagination, filtering, result format, or any edge cases.

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?

The description does not mention any parameters. Schema description coverage is 0%, so the description must compensate, but it adds no meaning beyond the schema's own descriptions.

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 the verb 'Search', resource 'notes', and platform 'Slite'. It distinguishes from siblings like 'get_note' (single note) and 'list_notes' (list all notes), but does not differentiate from other search tools on different resources.

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?

No guidance on when to use this tool versus alternatives like 'list_notes' or 'search_groups'. No exclusions or prerequisites mentioned.

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