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

Annotations indicate this tool is not read-only (readOnlyHint=false), implying it has side effects. The description does not mention side effects such as writing results to the user's workspace or making the report shareable, which likely creates objects. It does state the output is an interactive report URL, which is useful, but it doesn't disclose that the run may be persisted or have costs.

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 that conveys the main purpose and output type. It is concise without fluff. The reading is front-loaded with the main action and the output benefit. The note about 'tools_schema' is integrated naturally.

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 is moderately complex with nested objects and abstract parameters like 'column_mapping' and 'module_parameters'. The description points to 'tools_schema' for these, which is helpful. However, it does not explain the relationship to estimates (estimate_id) or how the output report integrates with the system. It is adequate but could carry more context.

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 parameters are documented. The description adds the important note to call 'tools_schema' for analysis-specific details within taskList.inputs. It does not add extra meaning beyond this, but the schema covers the basics. Baseline 3 is appropriate.

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 that the tool runs an analysis and returns a shareable report URL, which is clear in purpose. However, it is not specific enough to distinguish it from siblings like 'create_analysis' or 'modify_analysis'—the description does not mention that the tool executes an existing analysis definition, while create_analysis may set one up.

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 says to call 'tools_schema' first for analysis-specific fields, which is a usage hint. However, there is no guidance on when to use this tool versus 'create_analysis', 'modify_analysis', or 'rerun_package'. The distinction between these is not addressed.

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