subscriptions_info

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

With no annotations provided, the description carries the full burden, but it only states 'Get subscription information' without disclosing that this is a read-only operation, what data is returned, or any required permissions. This is insufficient transparency for a tool with no structured annotation support.

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 extremely concise at five words, with no redundant text. However, its brevity leaves out important context, so while it's well-structured, it's not as complete as it could be.

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 tool has simple parameters and no output schema, but the description doesn't explain what subscription information is returned or the meaning of 'subscription' in this context. The ambiguity is compounded by siblings like subscriptions_create/delete, and without annotations or output schema, the description is incomplete.

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 schema already provides descriptions for both parameters ('Event type' and 'Document ID') at 100% coverage, so the baseline is 3. The description adds no additional meaning about parameter semantics, and the schema descriptions are minimal.

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 'Get subscription information' clearly identifies the verb (get) and resource (subscription information), distinguishing it from subscription creation/deletion siblings. However, it doesn't specify the scope (e.g., document/event) or what information is returned, relying on the input schema for those details.

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 provides no guidance on when to use this tool vs alternatives. It doesn't mention that it's for viewing existing subscriptions, nor does it reference the sibling create/delete tools or any specific use case.

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