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

Discloses rate-limiting with 24h cooldown and that response includes 'retry_after_hours'. Mentions email fallback and push notification. Annotations indicate mutation (readOnlyHint=false) but no destructiveness (destructiveHint=false), and description adds behavioral details beyond annotations without contradiction.

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?

Four sentences, front-loaded with 'Parent-only.' Includes all essential information without verbosity. Every sentence adds value: who can use, what it does, when to use, rate limit info, and important warnings.

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?

No output schema exists, so description must explain return behavior. It covers rate limit error response with retry_after_hours and mentions sign-in requirement. Could be more complete by specifying success response format, but given the tool's simplicity, it's sufficient.

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 descriptions cover all three parameters (100% coverage), so baseline is 3. Description adds character limits (≤200 for reason, ≤280 for message) and optionality, which provides minor added value but doesn't fundamentally change understanding.

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 it sends a 'check-in' push notification and email fallback from parent to child. It specifies 'parent-only' and gives example use cases, distinguishing it from other tools like 'award_game_xp' or 'get_child_session_detail'.

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?

Provides explicit when-to-use scenarios with quoted phrases like 'remind my kid to study'. Includes important constraints: parent-only, requires sign-in, no spoofing. Lacks explicit when-not-to-use, but context is clear enough.

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