get_report_evidence_pack

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

With no annotations, the description carries more behavioral weight. It adds one useful behavior detail: the result is deterministic, meaning the generated evidence pack is reproducible. However, it does not explain important behavioral aspects such as whether this is a read-only/resource-consuming operation, whether it can fail, or what 'flags' semantically imply for the agent.

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 is concise, front-loaded with the core action, and contains no filler. The tradeoff is that brevity omits some needed behavioral details, but the text that is present earns its place.

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 output schema exists, so return values are not required in the description. Even so, the description lacks parameter-level guidance, clear exclusions, and deeper behavioral context. It is minimally usable but not fully complete for an agent that must decide among several related activity/report tools.

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 description coverage is 0%, so the description was expected to compensate, and it does not explain either parameter. Still, activity_id is clearly the identifier of the target activity, and include_environment is self-descriptive enough to infer its boolean intent, giving the parameter semantics a modest 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 uses the specific verb 'Build' and names a concrete deliverable ('deterministic facts, context, flags, and guidance for a post-activity Agent report'), so the tool's basic purpose is clear. It does not fully distinguish itself from report-related siblings like get_activity_summary or get_report_contract, so it falls short of a 5.

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 phrase 'for a post-activity Agent report' provides a clear, explicit use context: call this after an activity when generating an Agent report. It does not name alternative siblings, exclude related tools, or state when not to use it, but it does convey a direct context rather than leaving usage entirely implicit.

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