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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context — that only public content is returned and what a 'bukae' is on this platform — but says nothing about rate limits or the shape of the returned data.

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?

Front-loaded with the core action, followed by accepted input formats and a public-only constraint; every sentence carries useful information. The parenthetical explaining what a bukae is is slightly verbose but justifiable domain context for an unfamiliar app.

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 2-parameter read tool, the description covers scope, accepted inputs, and access limits. Since there is no output schema, a sentence sketching the returned fields (content, author, metrics) would have closed the remaining gap, but nothing needed to invoke the tool correctly 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?

Schema coverage is 100%, so baseline is 3, but the description goes beyond the schema's generic 'A bukaez.com link ... or @handle' by enumerating concrete URL path forms (/p/<id>, /@handle, /g/<id>, bukae.me/w/), which is real added meaning for the required target param.

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 and resource set — reads exactly one public post, bukae profile, or community — so an agent can tell it fetches a single known entity. It does not explicitly name bukaez_search as the alternative for discovery, so sibling differentiation is only implied by the word 'one'.

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?

Usage is implied by the accepted inputs (pass a link or @handle), but there is no explicit when-to-use/when-not guidance and no named alternative such as bukaez_search for keyword discovery. The 'Only public content is returned' constraint does give one useful boundary.

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