Advanced Performer Analysis

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

Annotations already declare readOnlyHint=true, so the read-only nature is clear. The description adds 'progress reporting and contextual logging', hinting at potential long-running behavior or side effects (logging). However, it does not disclose whether the tool is expensive, requires special permissions, or other behavioral traits beyond the 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?

The description is a single sentence, which is concise but lacks sufficient detail. It front-loads the purpose but does not earn its place with substantive content. A minimally viable description should be more informative without being verbose.

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 complexity (three parameters, no schema descriptions, existing sibling tools), the description is incomplete. It does not explain return values (though output schema exists) or provide enough context for an agent to use the tool correctly. The lack of parameter guidance is a major gap.

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?

The input schema has three parameters (performer_name, include_similar, deep_scene_analysis) with no descriptions. The description provides no information about these parameters, leaving their meaning and usage entirely unclear. With 0% schema description coverage, the description fails to compensate.

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 states 'advanced performer analysis' which vaguely indicates the tool's purpose but fails to specify what kind of analysis is performed. It does not differentiate from sibling tools like 'get_performer_info' or 'batch_performer_insights'. The phrase 'progress reporting and contextual logging' adds some context but remains ambiguous.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description does not mention prerequisites, exclusions, or specific use cases. An agent would have difficulty determining if this tool is appropriate.

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