ghl_saas_get_plan_deprecated

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds value by disclosing deprecation status and the required token type. No contradictions with annotations. It does not detail response format, but that is acceptable given the simple read operation.

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 somewhat verbose with repeated deprecation warnings ('DEPRECATED per spec' and bracketed note). It could be more concise by combining these. However, it is structured with deprecation, auth, and then purpose, making it readable.

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?

For a simple get operation with two required params and no output schema, the description covers deprecation, auth, endpoint, and version. It lacks clarification on the relationship between planId and companyId, but overall it is fairly complete for an agent to use or avoid this tool.

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 coverage is 100% with both parameters described. The description restates 'by plan ID' and 'filter SaaS plan', but adds no new semantic information beyond what the schema already provides. Baseline of 3 is appropriate.

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 'Get SaaS Plan' and 'Fetch a specific SaaS plan by plan ID', providing a specific verb and resource. It also explicitly marks the tool as deprecated and identifies the superseding endpoint, distinguishing it from siblings like ghl_saas_get_plan.

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 states that the tool is deprecated and superseded by a specific endpoint, guiding the agent to prefer the replacement. It also notes the required authentication level ('REQUIRES AN AGENCY-LEVEL (Company) TOKEN'), which is critical for correct usage.

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