show_modelcalendar

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

No annotations are provided, so the description must carry the full burden. It states 'Get' implying a read-only operation, but does not explicitly confirm safety (e.g., no side effects, read-only). It lacks disclosure of any behavioral traits such as required permissions, error behavior, or performance implications.

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 two sentences, both front-loaded with the primary action. Every sentence adds value: the first states the purpose, the second provides guidance on an alternative. No fluff or redundancy.

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 lack of annotations and output schema, the description is minimal. It covers the basic purpose and usage hint, but does not explain return format, potential errors, or data scope. For a simple retrieval tool, it is adequate but leaves some gaps.

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 100% description coverage for both parameters (workspaceId and modelId). The tool description does not add any additional semantic information about the parameters beyond what is already in the schema. With high schema coverage, baseline is 3.

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 clearly states the tool retrieves the model calendar including fiscal year settings. It uses the verb 'get' which precisely indicates a read operation, and the resource 'model calendar' is specific. The mention of 'set_fiscalyear' as an alternative distinguishes it from the sibling tool for changing the fiscal year.

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 explicitly tells when to use this tool (to get the model calendar) and when to use an alternative ('Use set_fiscalyear to change the fiscal year'). This provides clear usage context, though it does not elaborate on prerequisites or other conditions.

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