ponisha_my_dashboard

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds a genuinely useful behavioral trait beyond that: 'Some endpoints are slow (10-20s)', which affects timeout and retry planning. It does not mention auth requirements, pagination behavior across the list-type sections, or what a 'notifications_count' versus 'notifications' call returns in shape.

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 core enumeration is front-loaded in the first clause and every listed section earns its place by telling the agent what is available. The single long sentence is dense but readable, and the trailing latency warning is separated cleanly; minor cost is that the section list is packed into one run-on line.

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 six-parameter, ten-variant read tool with no output schema, the definition covers every section and flags the one operational hazard (slow responses). Gaps remain around return shapes for each section and how pagination behaves per section, but the annotations and schema fill most of the rest.

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?

Schema coverage is 50%, with role, status and desk_type already documented in the schema. The description adds only the note 'desk_type 0-2, meaning unverified' and does not explain page/per_page semantics or any section-specific parameter interactions. Baseline 3 is appropriate since the schema carries most of the parameter load.

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 gives a specific verb ('Read a section') plus the resource ('your dashboard') and enumerates all ten valid sections with brief parenthetical glosses such as 'workroom_summary (counts)' and 'my_projects (projects you posted as employer)'. An agent can map an intent to a section without opening the schema. It stops short of 5 because it never distinguishes this tool from overlapping siblings like ponisha_my_bids or ponisha_get_me.

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 parentheticals imply when each section applies (workroom_projects = projects you're working on/won), and the latency warning helps an agent decide if this is the right call. However, there is no explicit routing guidance such as 'use ponisha_my_bids instead for bid history' versus the workroom_bids section, so the agent must infer overlap with siblings.

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