Get my WAAS profile

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

No annotations are present, so the description carries the burden. It discloses the auth requirement ('Requires login'), signals a read-only operation via 'Fetch', and indicates data freshness with 'live'. It does not discuss errors or rate limits, but for a zero-parameter getter this is adequate.

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?

One sentence front-loads the action and resource, then compresses the field list with parentheticals and ends with the auth note. Every phrase earns its place.

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 no-argument read operation, the description tells the agent exactly what it will get (profile sections), whose profile ('your'), and what precondition is required (login). No output schema exists, but the field list provides the missing return-value context; no essential calling information is absent.

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?

There are zero parameters and an empty schema, so there is no parameter semantics to clarify; baseline 4 applies. The description instead explains what will be returned (experience, education, skills, share copy, preferences), which adds value beyond the 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?

States a specific verb ('Fetch'), a concrete resource ('your live Work at a Startup candidate profile'), and enumerates the major profile sections. The word 'live' separates it from draft/preview siblings, so an agent can distinguish intent even without opening the tool.

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 gives clear context: use it to retrieve the current saved profile, and it flags that login is required. It does not explicitly name alternatives like waas_preview_profile or waas_draft_profile, but 'live' and 'your' are enough to imply the appropriate use case.

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