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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the bar is lower, yet the description still adds real behavior: public visibility on the profile, a required "See your profile" (profile:read) permission, and a sign-in prompt when the member has not connected the platform. It also discloses the return shape as three booleans, which annotations alone would not provide.

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?

Purpose is front-loaded in the first sentence and the field definition follows immediately, so an agent reading only the first line can act correctly. It loses a little tightness to jargon ("Acts for your member") and a generic prompt-injection disclaimer that is boilerplate across the toolset.

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-parameter, non-destructive read with no output schema, the description covers everything an agent needs: what is returned, who can see it, what permission is required, and what happens when the member is unauthenticated. Nothing material 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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to add. The extra descriptive text about the residential/commercial/industrial booleans describes output values rather than inputs, which does not lower the score but also does not add input meaning.

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 a specific verb and resource ("Read your member's Work sector") and immediately defines what that resource contains — residential, commercial and industrial flags, each boolean. That pairs it cleanly against the sibling update_my_work_sector and leaves no ambiguity about what is returned.

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 conveys context ("as their profile editor reads them", "Public on their profile") which implies this is the read path for the member's own sector data, but it never states when to prefer it over alternatives or when not to call it. Usage is inferred rather than stated.

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