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

The description goes well beyond the readOnlyHint and idempotentHint annotations. It discloses role-based access differences, locale handling, and what content is excluded (event bodies, timeline introduction/conclusion) for non-admins. This provides rich behavioral context that annotations alone do not convey.

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 a single, dense paragraph that front-loads the core purpose and then efficiently covers role-based differences and data exclusions. Every sentence carries meaningful information without redundancy or filler.

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?

The tool has role-based complexity, locale sensitivity, and specific field exclusions. The description thoroughly covers these aspects. An output schema exists, so return values are not needed in the description. The description is complete for the tool's complexity.

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%, so baseline is 3. The description adds extra nuance for the locale parameter, explaining that it should be the caller's language and that it's ignored for admin tokens. This adds meaning beyond the schema's enum description, justifying a score above baseline.

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 opens with a specific verb and resource: 'Returns one published timeline.' It clearly states the resource type and the action, and then provides details on role-based behavior (administrators vs. other accounts) that distinguish the response. This is specific and unambiguous.

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 gives clear context on when to use the tool: to retrieve a single timeline by ID. It doesn't explicitly mention alternative tools or when not to use it, but the purpose is so focused that context is sufficient. It also explains role-specific behavior that guides correct usage (e.g., admins get bilingual, others need locale).

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