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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior. The description goes beyond this by detailing the output fields, the fact that the current org is marked within the orgs list, and the connection-follows-org-switching behavior, which adds meaningful behavioral context without contradicting 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?

The description is two sentences: the first states the tool's output and the second provides essential usage logic. It is front-loaded and every sentence earns its place, with no redundant filler.

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 zero-argument, read-only tool, the description is complete: it enumerates the expected output fields and gives a concrete workflow directive (check before publishing, compare org id). No output schema exists, but the description sufficiently covers what the agent needs to call and interpret the tool.

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 has zero parameters, and the schema is empty, so the baseline is 4. The description confirms 'Takes no arguments,' which adds no new semantics but also requires no parameter documentation.

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 clearly states the tool reports the account and organization the connection is signed in as, listing specific fields (user id, email, name, org id/name, and orgs). This distinguishes it from the sibling app-management tools, which all target app operations rather than identity/connection context.

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?

The description provides concrete usage guidance: call before publishing when the person named an organization to publish into, and stop if the org id doesn't match, with switching done at reachpad.dev/apps. It lacks explicit alternatives or when-not-to-use guidance, but the context is clear enough to direct an agent.

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