search_document_drafts

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety profile is covered. Description adds the 'editable' and 'Morning' context, which is useful, but omits pagination behavior, result sorting, and whether it searches by content or metadata. With annotations carrying the main burden, a 3 is appropriate.

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?

A single, front-loaded sentence with zero waste. Every word contributes to the purpose.

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?

Adequate for a basic read-only search tool with annotations covering safety and a simple schema, but the description offers no guidance on when to use it versus related draft tools, no mention of pagination, and no indication of result format. It is minimally viable 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?

Schema coverage is 0%, but only 2 parameters exist (page, pageSize) with defaults and constraints. The description does not mention pagination at all, which is a gap, but for a simple paginated search the schema's default values are fairly self-explanatory. Baseline 3 applies for low param count with minimal compensation needed.

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?

Clear verb 'search' + resource 'document drafts' with scope 'editable' and location 'in Morning'. Distinguishes from siblings like get_document_draft (single fetch) and search_documents (probably finalized documents), though explicit sibling differentiation is absent.

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 when-to-use guidance, no alternatives named, no exclusions. The agent must infer that this is for finding drafts vs. fetching a specific draft by ID.

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