plane-user-profile-get

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

Clearly indicates it's a read operation with no side effects. Lacks explicit mention of authentication requirements, but the description is sufficient for a simple getter given no 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?

Single sentence with front-loaded verb and resource, followed by a concise list of fields. No wasted words.

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?

Adequately describes purpose and output for a zero-parameter tool. Could mention that it requires an authenticated session, but not strictly necessary.

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?

No parameters, so baseline 4 per rubric. Adds value by enumerating returned fields, which is not in the empty input schema.

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?

Clearly states verb 'Get', resource 'current user profile', and lists specific fields returned (display name, avatar, theme, onboarding state). Distinguished from sibling plane-user-profile-update.

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?

Implies usage as a read-only profile retrieval, but does not explicitly state when to use versus alternatives like plane-auth-status or plane-user-profile-update. No exclusion criteria.

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