ciso_assistant_api_task_templates_calendar_retrieveRetrieves calendar task templates for a given start and end date range, so you can review scheduled compliance and security activities within a specific period.
Generic export mixin for CSV/XLSX exports.
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | ||
| start | Yes |
Changes observed during successful MCP inspections.
v2.3.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotentHint true, so the description needed to add calendar-specific behavior. Instead it describes an export mixin, giving no information about what data is returned, how the date window is applied, or any limits. The text is misleading even though it does not literally contradict readOnlyHint.
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?
It is a single short sentence, so there is no bloat, but that brevity comes from describing the wrong thing rather than from disciplined specification. Being short and wrong is not conciseness.
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?
With no output schema, two undocumented required parameters, and a description that discusses an unrelated export mixin, an agent has essentially nothing needed to invoke this tool correctly.
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% and both required parameters (start, end) are bare strings. The description does not mention them at all, leaving their format, timezone, inclusivity, and range semantics completely undocumented.
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 says 'Generic export mixin for CSV/XLSX exports', which does not describe this tool at all. The tool is a calendar retrieval for task templates taking start/end dates, yet the text describes an unrelated export mixin, actively misleading the agent about what it does.
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 guidance on when to use this tool, no mention of alternatives such as ciso_assistant_api_task_templates_export_csv_retrieve or ciso_assistant_api_get_governance_calendar_data_retrieve, and no context for the required date range.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.