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

With readOnlyHint=true and idempotentHint=true already declared, the description adds real value: 'opens nothing by itself' confirms zero side effects, and it discloses the return content (screens, buttons, fields). The note about partner-only APIs further explains why no direct write path exists.

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?

Three sentences, but the front-loaded first sentence misleads about the action and the correction only arrives mid-paragraph. The closing sentence on SiteMinder's partner API is long and only indirectly relevant to invoking the tool.

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 parameterless, read-only guide tool with annotations and no output schema, the description covers what it returns and how to continue the task. The one gap is that it never says what the agent should pass along or how the specific account/property context is established.

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?

There are zero parameters and the schema is fully self-describing, so the baseline is 4. The description correctly implies no inputs are needed, though it never states how the target account or rate context is determined.

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 states a specific resource (rates in the user's SiteMinder account) and, crucially in the second sentence, reveals the actual behavior: it returns step-by-step instructions rather than performing the update. That nuance is what separates it from a real mutation tool, though the leading 'Update rates...' phrasing briefly implies the opposite and no sibling (siteminder_update_inventory, siteminder_close_dates) is named for differentiation.

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?

It gives explicit downstream guidance ('then do it with the cotlet_browser_* tools in the user's SiteMinder Cloud Browser') and explains why the official API is not an option (partner-only, certified APIs). It does not tell the agent when to pick this versus the sibling SiteMinder update tools, but the workflow context is clear.

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