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

Annotations already declare readOnly/idempotent/safe behavior. Description adds valuable cost disclosure ('Free') and content scope transparency (listing all contained data types). Also clarifies this aggregates data across a multi-stage pipeline, which helps agents understand the relationship between this tool and other ceevee_* operations.

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 with zero redundancy: (1) core capability with specific return values, (2) parameter sourcing, (3) pipeline context, (4) cost. Information is front-loaded and every sentence earns its place without repeating schema or annotation data.

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 presence of an output schema and comprehensive annotations, the description provides appropriate completeness. It adequately explains the complex multi-stage pipeline context and enumerates all major data categories returned, fulfilling its obligation for a retrieval tool with rich structured metadata.

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?

With 100% schema coverage, baseline is 3. Description exceeds baseline by specifying the semantic source of the session_id parameter (which upstream tools generate valid IDs), helping agents understand data lineage and prerequisites beyond raw type information.

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 uses specific verb 'Get' with resource 'positioning session detail' and enumerates exact components returned (analysis, lens, opportunities, targeted edits, PDF URLs). Clearly distinguishes from sibling list operation (ceevee_list_positioning_sessions) and specific component getters (ceevee_get_opportunities) by emphasizing 'full' detail and comprehensive content.

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 clear parameter sourcing ('session_id from ceevee_list_positioning_sessions or from ceevee_analyze_positioning') and pipeline context ('analyze -> opportunities -> confirm-lens pipeline'). However, lacks explicit guidance on when NOT to use it (e.g., no mention to use specific getters like ceevee_get_opportunities if only partial data is needed).

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