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

Annotations only declare it as a read-only, open-world operation, but the description adds substantial behavioral context: values load live from the workspace's own system via integrations, only fields marked 'AI can see this' are returned, and an empty list is a legitimate result that the agent cannot fix. That empty-result and permission-gating disclosure is exactly what an agent needs to avoid misreading a blank response.

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, each doing distinct work: what is returned, the field-visibility rule with its empty case, and the logged-in precondition. Front-loaded with the resource, though the middle sentence is dense and slightly awkward.

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 one-parameter read tool with no output schema, the description covers the return shape, the permission model, the empty-result case, where the setting is controlled, and the calling precondition. Nothing essential is missing.

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?

With schema coverage at 100%, the schema already documents ticket_id thoroughly (uuid, from list_tickets, not the number). The description adds no parameter-level detail, so baseline 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?

States a specific resource (customer details for a ticket) and what comes back (details plus the buttons that can be pressed), so an agent can tell it apart from get_ticket or list_buttons by scope. It never names a sibling explicitly, so it stops short of full 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?

Provides one meaningful precondition: 'Only for a customer who was logged in.' That tells the agent when the tool is applicable but gives no alternative tool to use when the condition fails, and no when-not-to-use guidance beyond that single gate.

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