export_weekly_report

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only states that the tool 'Exports' a report, but does not clarify whether the report is returned, saved as a file, or sent somewhere. It also leaves the term 'PMC summary' undefined and does not mention any dependencies on recent activity data or side effects.

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 of 9 words, directly stating the verb and object with no redundant or filler content. It is appropriately sized for a simple tool with no parameters and no output schema.

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 tool's low complexity (zero parameters, no output schema, no annotations), the description is minimal but leaves key details unclear, such as what 'PMC' stands for and how the export is delivered (returned, file, etc.). For a zero-parameter tool, a bit more context about the report's content and delivery would make it fully complete.

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 zero parameters, so the description is not required to add parameter-level detail. The baseline for zero-parameter tools is 4, and the description confirms that no parameters are needed by simply stating the action and content of the report.

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 'Exports' and identifies the resource as 'weekly performance & PMC summary report' with the output format 'GitHub Markdown.' This clearly distinguishes the tool from the sibling analysis and retrieval tools, which focus on getting, analyzing, or calculating data rather than exporting a report.

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?

There is no guidance on when to use this tool versus the many siblings, nor any mention of alternatives, prerequisites, or exclusions. The description simply states the function without providing context for choosing it over other tools.

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