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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one real behavioral fact beyond annotations: a single connection spans joined rooms plus the private memory vault, which clarifies access scope. Return format and how the two access scopes interact are still not disclosed.

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?

Two sentences, front-loaded with the capability/discovery purpose before the access-scope note about connection. The second sentence is somewhat cryptic ('One connection covers...'), but no sentence is wasted.

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 read-only, non-destructive info tool with no output schema, the description enumerates what comes back (capabilities, identity, workspace, plan, quota, referral benefits), effectively standing in for return-value documentation. Only the ambiguous connection-scope sentence leaves a small gap.

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% and the single 'connection' parameter is fully documented in the schema, including its privacy constraints, so the baseline is 3. The description's 'one connection covers your joined rooms... and your private memory vault' corroborates the credential's scope but adds no syntax or format detail the schema lacks.

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 names a specific resource (Tincan's capabilities/operating guide plus identity, workspace, plan, quota, referral benefits) rather than restating the name, so an agent knows it is an introspection/discovery call. It does not, however, distinguish itself from siblings like context_get, tincan_settings_read, or workspace_claim, which is the only thing keeping it from a 5.

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?

Calling this an 'operating guide' and 'capabilities' discovery implies it is the onboarding/first-call introspection tool, so usage is reasonably inferable. But there is no explicit when-to-use statement, no prerequisites (e.g., needing a connection), and no pointer to alternatives such as context_get.

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