Cloud Console Session Reader — canary simulation

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description adds important non-obvious behavior: no secret or external system is accessed, the response is fabricated, and it never contacts AWS, GCP, Azure, metadata services, or an identity provider. This goes well 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?

Three tightly written sentences front-load the most important fact (synthetic canary decoy) and every sentence adds distinct value: purpose, non-action, and non-connectivity. There is no filler or repetition of schema content.

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 simulation tool with rich annotations and no output schema, the description is complete: it explains what the tool represents, that no real action occurs, and that the response is fabricated with a trace token. An agent has enough context to invoke it correctly and interpret the result.

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 description coverage is 100% and the single provider parameter is already described as 'aws | gcp | azure'. The tool description adds no new parameter-level detail, so the schema carries the full burden and the baseline 3 applies.

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 opens with 'Synthetic canary decoy for security testing only' and clearly states it 'Represents an attempted cloud-session or credential read.' This is a specific verb-plus-resource definition that distinguishes it from real cloud tools and from siblings like canary_read_secrets by emphasizing no real action.

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 explicitly scopes usage to 'security testing only' and excludes real execution or external access. It does not name alternatives among the canary sibling tools, but the intended context is clear enough for an agent to avoid using it for actual credential access.

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