Parse Birth Details

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

Annotations declare readOnlyHint=true, and the description adds that extraction is 'conservative' to avoid guessing, plus discloses the 'missing' return field. No contradictions with annotations.

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: first states purpose and fields, second explains behavioral trait and agent guidance. Every word serves a purpose, no redundancy.

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 single-parameter schema and no output schema, the description adequately explains what the tool returns (fields plus missing list). No mention of output format, but the behavioral notes are sufficient for an agent to use it effectively.

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 100% with one parameter described. The description adds a concrete example ('born 26 Dec 2019, 9:15 am, Delhi'), enhancing understanding beyond the schema's description.

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 the verb 'extract' and resource 'birth details' from a 'short operator note'. It specifies the exact fields (dob, tob, place, lat, lon, timezone), distinguishing it from sibling tools that calculate or manage client profiles.

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 explains that the tool returns a 'missing' list for unparseable fields, guiding agents to ask the operator for clarification. While it doesn't explicitly contrast with siblings, the context implies usage when extracting from notes vs. retrieving existing profiles.

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