tokportal_get_analytics_contract

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description correctly aligns with a safe, read-only operation. The description adds value by specifying the exact payload structure (contract, access, metrics semantics, etc.), which goes beyond the annotations.

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 very concise — two sentences providing the core action and then a simple list of return components. Every piece adds value without 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 zero parameters, no output schema, and clear annotations, the description adequately covers the tool's purpose. It explains what the contract contains, which is sufficient for an agent to decide when to use it. Could be improved by hinting at whether this is a prerequisite for other analytics operations.

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 with 100% coverage. The description explains the tool returns a contract object, which aligns with parameterless behavior (no input needed). The description semantically adds that this is a metadata lookup, not requiring any arguments.

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 it returns an 'analytics data contract' and lists specific components (metrics semantics, freshness targets, redaction rules). However, it could better distinguish from sibling tools like 'tokportal_get_analytics_dashboard' or 'tokportal_get_analytics_account', which also deal with analytics data.

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 implies this tool is for retrieving the structural contract of analytics data, not the actual data itself. However, it does not explicitly state when to use this versus other analytics tools (e.g., for understanding data model vs. fetching metrics). No alternatives or exclusions are mentioned.

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