Get Analysis Results

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

Annotations (readOnlyHint=true, idempotentHint=true) align with 'Retrieve'. Description discloses return contents (engagement metrics, audience demographics, etc.) beyond annotations. Lacks mention of error handling for invalid IDs but overall sufficient.

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?

Description is efficiently structured with clear sections, but could be slightly more concise. Front-loaded with primary 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?

Given one parameter, no output schema, and comprehensive annotations, the description fully covers usage: return contents, alternative tool, and parameter source.

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?

Only one parameter 'analysis_id' with 100% schema coverage. Description adds value by stating 'The UUID of the analysis (from influiq_start_analysis)', clarifying its origin beyond schema's 'Analysis UUID'.

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 explicitly states 'Retrieve the full results of a completed influencer analysis' with a specific verb and resource. It distinguishes from sibling tool 'influiget_analysis_progress' by noting that for progress, use that tool.

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 alternative: 'If the analysis is still processing, check status with influiq_get_analysis_progress.' Also prerequires analysis_id from 'influiget_start_analysis', clarifying the source of the parameter.

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