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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: an explicit negative guarantee ('Never returns credentials or webhook signing secrets') and the authentication requirement, both of which an agent cannot infer from structured fields. It stops short of noting whether the response can be empty or partial for an unconfigured workspace.

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 short sentences, front-loaded with what is returned, then the security caveat, then the auth requirement — a sensible ordering. The middle clause listing downstream features is the only sentence that does not clearly earn its place, since it reads as marketing rather than guidance.

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?

An output schema exists, so return structure need not be described, and the description covers the two things the schema cannot: auth prerequisite and the exclusion of secrets. For a zero-parameter read tool this is close to complete; only the failure/empty-state behavior for an unconfigured workspace is unaddressed.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not invent parameters or imply filtering options that do not exist.

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?

Opens with a specific verb ('Read') and enumerates the exact fields returned (profile name, workspace name, default sender, website links), so an agent knows precisely what this yields. The trailing clause ('for account security, member invitations and API-key management') blurs the line between returned data and use case, slightly muddying an otherwise crisp purpose. No sibling in the list overlaps this resource, so differentiation is not a problem.

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?

States the prerequisite 'Workspace authentication required', which is genuine usage context. However, it never says when to reach for this tool versus other read tools (e.g. get_connection_status, get_billing_history) or what to do if authentication is missing. Usage is implied rather than directed.

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